BUGZILLA VS JIRA SOFTWARE
BUGZILLA VS JIRA CODE

Maybe they tried building workflows in Bugzilla and didn’t make it work. You end up optimizing for similar but distinct use cases as it might become more important to report about issues than it is to file and fix and close them.Īnd that’s the state Mozilla might be finding itself in right now as a few teams here and there try to find the best tools for their garden and settle upon Jira.

BUGZILLA VS JIRA SOFTWARE

Regardless of why, once they become Workflow Management Software they become incomparable with Issue Trackers. Perhaps because the people in charge of the customization are interested more in workflows than in Issue Tracking? And every time Jira or MKS is customized it seems to stop being Issue Tracking Software and start being Workflow Management Software. In other words, to make the switch the new thing needs to do something that the previous one couldn’t, wouldn’t, or just didn’t do (or you’ve forgotten that it did). But they couldn’t just be “perfectly adequate”, they had to be better enough than what they were replacing to warrant the switch. They had id numbers, relationships, state, attachments, comments… all the things you need in an Issue Tracker. With minimal customization, Jira and MKS Integrity both seemed to be perfectly adequate Issue Tracking Software. We started with an outdated version of FogBugz, then we had a Bugzilla fork for the WebKit porting work and MKS Integrity for everything else across the entire company, and then we all standardized on Jira. While I was on the Browser team at BlackBerry I used a variety of different Issue Trackers. An Issue Tracker is a tool that helps us all coordinate work.Īnd group things require cooperation, agreement, and compromise.

BUGZILLA VS JIRA CODE

The code lives Out There, the garden is Outside… but the tools are in our hands.īut tools can also be group things. They’re the part of our work that we actually touch. Tools are personal things: they’re the only thing that allows us to express ourselves in our craft. The distributed nature of the organization and community means that teams and offices and any informal or formal group is its own tiny experimental plot tended by gardeners with radically different tastes.Īnd if there’s one thing that unites gardeners and tech workers is that both have Feelings about their tools. It seems as though Mozilla is never not in a period of transition. This Week in Glean: The Three Roles of Data Engagements.This Week in Glean: How Long Must I Wait Before I Can See My Data?.This Week in Glean: What If I Want To Collect All The Data?.

Bugzilla vs jira