The problem with this approach was that there were some MTOS cases that shouldn't have been public (because, for example, they might have a user's email address or other sensitive information, or relate to security vulnerabilities that had not yet been publicly disclosed) There are also many cases that are MT Internal that non-Six Apart employees should be able to see, like bugs and patches that impact enterprise consultants and developers.
Going forward, instead of MT Internal and MTOS, the MT fbz instance will instead have two projects, one public and one private, both of which can contain bugs in both the open source and proprietary portions of the product. To reflect this change, the MTOS project name has been changed to "Movable Type-External."Â
This shouldn't change too much for the MT community, but it means that if you wish to enter a bug report for the Pro or Enterprise components of the product, you can do that directly instead of filing a case in the MTOS project, then having the case seemingly disappear when it was moved to MT Internal.Â
If you have any questions or concerns about these changes, or anything else relating to MT case management process, please let us know in the comments to this post.Â
mrsjanet on December 19, 2008, 12:50 a.m. Reply
It just makes sense to not make certain thing public when it comes to security. Plus with how great Movable Type is I am sure there is not much the rest of the community is missing out on seeing!
Coleen York on July 17, 2012, 4:56 a.m. Reply
I don’t know. It is not good some bugs in security to be hold off the public view. Of course, I won’t change my mind. I still believe in and use MT, but this is not good.
Anna Kokoeva on August 6, 2012, 12:05 a.m. Reply
FogBugz is a great tool for finding bug. I am 100% sure you from MT are knowing what you are doing.
male extra on September 5, 2012, 3:35 a.m. Reply
I totally agree. FogBugz is a great little tool and it’s helped me out on more than a few occasions.
Gore on September 20, 2012, 11:53 p.m. Reply
Does it mean that we need to have another registration with FogBugz? If so it is really uncomfortable. We need to have a registration on MT and for report a bug another one on FogBugz!
agnessita on October 17, 2012, 6:05 a.m. Reply
I don’t think FogBugs is the best tool for finding bugs as some of the previous commenters have said. It is just a regular program with functions like many other on the market. Don’t get me wrong. I have nothing against FogBugs or their co-work with Moveable Type. I’m just saying it is like all the others.
Amanda Pierson on October 23, 2012, 11:17 p.m. Reply
OK, but how we will keep the records for the bugs if they disappear when have been solved?
Peter Peterson on November 2, 2012, 8:31 p.m. Reply
This FogBugz reorganization is not good at all. All previous bugs reports are with broken links and we can’t see the information about the bugs nor the comments from other members. The links lead to FogBugz main page which is not useful at all.
Fern on November 12, 2012, 9:14 p.m. Reply
You are able to see the details about every bug in FogBugz, but you need to log in with your FogBugz user name and password. Then the details will be given to you.
Harry Cohen on December 14, 2012, 4:50 p.m. Reply
It was a right decision. I caused some unwanted mess, but the security in bugs is the most important thing. When we posted the bugs here on the site of Movable Type everyone could see them and use it in their own purposes. Now it can’t be done with FogBugz which is great.
Rupert Boneham on December 24, 2012, 3:55 a.m. Reply
In opposite to all strange comments above I should say that FogBugz made the thing far more tidy than before. Now everything is better and I like the move you have made few hours ago.