Bugzilla 3.4 will have rudimentary support for saying that a bug is related to a bug in another bug-tracker. Currently the development version allows you to input Bugzilla and Launchpad bugs, and we'll probably allow Trac and Jira in some future version, too.
Future versions will also automatically update the other bug tracker, if possible, to let them know that you've set a relationship to their bug.
The relevant bug for tracking development on this feature is here:
Bugzilla does have time-tracking, you just have to set the timetrackinggroup parameter.
Products can be hidden by setting them as Mandatory/Mandatory for a group that nobody is in. You can also close them to entry and they won't appear on the New Bug page.
-Max
To clarify, this comment was more me attempting to be amusing than an actual factual statement. I suspect there were actually many advanced systems in use and I really actually have no idea what systems were being used.
-Max
I just wanted to say that the above comment is actually my opinion and not a representation of any government organization or employee, and I am not an government employee.
There were existing PRACA systems before the one we made. One of the other responders is correct that there are many other mitigating forces in mishaps, and that my statement may not be correct.
-Max
They were using something like 40 different systems--a different one for practically each department and contractor at NASA. Some of them were pretty much using the technological equivalent of post-it notes next to their screens, and I've been told that some were keeping track of defects using paper files.
-Max
My company (Everything Solved), made PRACA along with NASA, and in one of the first meetings, a researcher at Ames told me that if a system like PRACA had always existed at NASA, then every major mishap in NASA's history could have been avoided.
-Max
You know, I'm one of the primary developers of Bugzilla, and I agree with you! It absolutely could use some UX love.
One problem is that UX engineers are kind of hard to come by. Most of them get paid a lot of money and work all day, and I know few of them who work on open source projects in their spare time.
We have some good programmers on the team, but we're not all UI designers. I have some UI design experience myself, but I'm usually caught up in doing architecture and backend. We do consider improving Bugzilla's UI to be a high priority, though.
Well, it was more of a post exploring whether or not there would be advantages and if it could all be done iteratively without a re-write. I'm big on iterative development--to a large degree, I spearheaded a lot of the recent iterative improvements to Bugzilla.
I used to need fifteen hours of sleep a night. Then, I completely cut sugar out of my diet. Not only did it make me more lively during the day, now I only need 6 - 8 hours of sleep a night, provided that I keep a regular schedule.
Slashdot Mirror
Bugzilla 3.4 will have rudimentary support for saying that a bug is related to a bug in another bug-tracker. Currently the development version allows you to input Bugzilla and Launchpad bugs, and we'll probably allow Trac and Jira in some future version, too.
Future versions will also automatically update the other bug tracker, if possible, to let them know that you've set a relationship to their bug.
The relevant bug for tracking development on this feature is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=bz-seealso
-Max
Bugzilla does have time-tracking, you just have to set the timetrackinggroup parameter. Products can be hidden by setting them as Mandatory/Mandatory for a group that nobody is in. You can also close them to entry and they won't appear on the New Bug page. -Max
To clarify, this comment was more me attempting to be amusing than an actual factual statement. I suspect there were actually many advanced systems in use and I really actually have no idea what systems were being used. -Max
I just wanted to say that the above comment is actually my opinion and not a representation of any government organization or employee, and I am not an government employee. There were existing PRACA systems before the one we made. One of the other responders is correct that there are many other mitigating forces in mishaps, and that my statement may not be correct. -Max
They were using something like 40 different systems--a different one for practically each department and contractor at NASA. Some of them were pretty much using the technological equivalent of post-it notes next to their screens, and I've been told that some were keeping track of defects using paper files. -Max
My company (Everything Solved), made PRACA along with NASA, and in one of the first meetings, a researcher at Ames told me that if a system like PRACA had always existed at NASA, then every major mishap in NASA's history could have been avoided. -Max
You know, I'm one of the primary developers of Bugzilla, and I agree with you! It absolutely could use some UX love.
One problem is that UX engineers are kind of hard to come by. Most of them get paid a lot of money and work all day, and I know few of them who work on open source projects in their spare time.
We have some good programmers on the team, but we're not all UI designers. I have some UI design experience myself, but I'm usually caught up in doing architecture and backend. We do consider improving Bugzilla's UI to be a high priority, though.
-Max
Well, it was more of a post exploring whether or not there would be advantages and if it could all be done iteratively without a re-write. I'm big on iterative development--to a large degree, I spearheaded a lot of the recent iterative improvements to Bugzilla.
-Max
The site itself doesn't say that at all.
-Max
I used to need fifteen hours of sleep a night. Then, I completely cut sugar out of my diet. Not only did it make me more lively during the day, now I only need 6 - 8 hours of sleep a night, provided that I keep a regular schedule.
-M