JIRA is a commercial issue tracker (issues can be bugs, feature requests, improvements, tasks, etc). For comparison, Bugzilla is a bug tracker.

Many ASF projects are currently using JIRA, and other projects are encouraged to migrate, but the choice is entirely up to the project committers

More information on JIRA is available on the Atlassian website.

Q: How do you pronounce JIRA?

Q: Where is it installed?

Q: Will my project be forced to use JIRA?

Q: How do I get my ASF project using JIRA?

Q: How does a JIRA Administrator create a new project?

Q: How do permissions work in JIRA?

Q: Why bother migrating to JIRA? What's wrong with Bugzilla?

Q: Why would people prefer JIRA?

From Jeff Turner (an ASF committer and Atlassian employee):

 >> Jira ... has anyone used it? What was the experience? 
 >["Jira"] is generally claimed to have a nicer UI and better overall features. 
 > Once logged in, you can configure your front page ('dashboard') to 
 > display only the projects you're interested in, including saved search 
 > results (eg "New issues this week", "Issues assigned to me", etc).  Other 
 > neat stuff: 
 >  - Saved searches can be shared between users, and 'subscribed' to 
 >    (generating a periodic email of results). 
 >  - Search results viewable as RSS, allowing neat integration tricks.  Eg. 
 >    use <xslt> to generate release notes, or display latest bugs on the 
 >    website: http://xml.apache.org/forrest/forrest-issues.html 
 >  - Interaction via email: reply to a change notification email, and your 
 >    reply will appear as a comment in the issue. 
 >  - Commit emails mentioning a bug can have their comments appear in the 
 >    mentioned issue. 
 >  - Various reports: changelogs, roadmaps, 'popular issues'. 
 > ASF projects like Maven, Jelly, Geronimo, Forrest, etc had been voting 
 > with their feet, using on codehaus.org's Jira.  Hence we've established 
 > an ASF Jira to accommodate projects' preferences. 
 > There are various public Jira instances you can poke around with to form 
 > an opinion: 
 > http://jira.atlassian.com/      # Tracks jira bugs; has a test project for experimentation 
 > http://issues.apache.org/jira/  # Just established - used by Geronimo, Phoenix, Jelly, etc 
 > http://jira.codehaus.org/       # Various codehaus projects, and Maven
 > http://issues.cocoondev.org/    # Forrest :) 
 > http://jira.opensymphony.com/ 
 > http://opensource.atlassian.com/projects/spring/

To this list of advantages one can now add "email threading" - when someone comments or updates an issue, the notification email is "in reply to" the original issue creation email. Thus "sort by thread" is a quick and easy way to see all actions on an issue. This is of particular use in established projects where a large percentage of discussion is oriented about bugs or patches in the issue tracker.

Highly subjective answers to '''real questions'''

These are also from Jeff, an Atlassian employee & ASF committer:

Q: JIRA isn't Open Source! Why would free Apache projects use a commercial bug tracker when free alternatives exist?

Q: Won't using free alternatives encourage them to improve?

Q: What are the benefits of using/encouraging non-free software?

The choice is up to individual projects. Projects can be migrated at any time, so there is no pressure.

ApacheJira (last edited 2011-03-26 12:21:08 by SebastianBazley)