For someone not in the group, they would not see the checkbox at all and the bug would be public. To manually uncheck it before submitting. The other thing is that we can set a specific group to be on by default for people in the group when filing the bug so that they would need Unless we hack in some code in the BMO extension to add the group manually based on the component after the bug is submitted. The issue is that if you want different mandatory permissions per component, we have to do different products. > So, what's the best way to accomplish "A bug gets filed, and by default it > It'd be things like employee contracts, expenses, hr matters, etc. > for MoFo Operations is something that should only be seen by the Ops group. > I think Angela's concern was that pretty much every bug that will be filed > Angela's out sick this week, so attempting to put words in her mouth. (In reply to Jon Buckley from comment #7) List of users to be placed in the new team group should be the admin for the new group (bless rights) that will be able place others in the team group years ago Whether a specific account or mailing list should be automatically cc'ed when a bug is placed in the new group (optional): None Which products need to have the new group enabled: Mozilla Foundation Operations Name for the new group: Mozilla Foundation Operations The list of suggested reviewers for the review flag (optional, uses the product's review suggestions by default): None. The product it should go in: Mozilla Foundation OperationsĪ longer description: Bugs for the Mozilla Foundation Operations teamĭefault assignee: ' as above for QA contact.Įmail addresses for whoever should be CC-ed to every bug in the component: N/AĪny flags (bug and/or attachment) that will need to be visible for bugs against the new component: the Default needinfo and review flags The list of suggested reviewers for the review flag (optional, empty by default): N/A If you want review requests to require a reviewer (optional, false by default): N/A The number of votes needed to confirm a bug (UNCO -> NEW) (optional, disabled by default): N/A The security group(s) bugs should be classified under when a user checks the security flag (if you don't know, we can help figure this out for you): we need a security group for MoFo Operations bugs. The initial list of target milestones, with their info (see below): None The initial list of versions, with their info (see below): None The initial list of components, with their info (see below): General The classification (group) you would like the product in: OtherĪ longer description, usually including a web link for more info on the product: Bugs for the Mozilla Foundation Operations team Simply takes me less time to find what I need compared to our new system.The name of the product: Mozilla Foundation Operations Little secret: even though all data from Bugzilla was copied to our new bug tracker when we made the switch, I still tend to go first to Bugzilla if I need to find an old bug. For the rare cases where it doesn't, the "Advanced Search" definitely does the job, while really being "advanced" but in no way "complicated". Usually, jotting a keyword or two in the "Simple Search" is enough to find exactly what you need. This is a point where OTRS definitely scores. One of the key aspects of a bug tracker is definitely the performance of its search functionality. Even some of our sales guys were easily and independently filing new bugs or searching for existing bugs, and that's definitely saying something. This implies there is no or only minor explanation needed to get started with Bugzilla. The most common things are but a click away. No options hidden behind mysterious hamburger menus or gear wheel icons. No need to navigate through different submenus to do even the simplest of tasks. Very simple and clean, everything does what you expect it to do. It's a school book example of how great free and open source software can be. To cut right to the chase: as a user / bug reporter, Bugzilla was a dream to work with. Up until about a year ago, Bugzilla was the bug tracking application used in our company.
0 Comments
Leave a Reply. |