|Stable release||6.3.8 / October 13, 2014|
|Type||Bug tracking system, project management software|
|License||Proprietary, free for use by official non-profit organizations, charities, and open-source projects, but not governmental, academic or religious organizations|
JIRA (// JEE-rə) is a proprietary issue tracking product, developed by Atlassian. It provides bug tracking, issue tracking, and project management functions. Although normally styled JIRA, the product name is not an acronym, but a truncation of Gojira, the Japanese name for Godzilla. It has been developed since 2002.
JIRA is written in Java and uses the Pico inversion of control container, Apache OFBiz entity engine, and WebWork 1 technology stack. For remote procedure calls (RPC), JIRA supports SOAP, XML-RPC and REST. JIRA integrates with source control programs such as Subversion, CVS, Git, Clearcase, Team Foundation Server, Mercurial, and Perforce. It ships with various translations including English, Japanese, German, French, and Spanish.
According to Atlassian, JIRA is used for issue tracking and project management by over 25,000 customers in 122 countries around the globe. Some of the organizations using JIRA for bug-tracking and project management are Linden Lab, JBoss, Spring Framework, Hibernate, Fedora Commons and Skype. The Apache Software Foundation uses JIRA and Bugzilla. Projects currently using Bugzilla have the option of migrating to JIRA at any time.
JIRA is a commercial software product that can be licensed for running on-premises or available as a hosted application. Pricing depends on the maximum number of users, typically $50 per user for in-house and $7 per month per user for the hosted version.
Atlassian provides JIRA for free to open source projects meeting certain criteria, and to organizations that are non-profit, non-government, non-academic, non-commercial, non-political, and secular. For academic and commercial customers, the full source code is available under a developer source license.
In April 2010 an XSS vulnerability in JIRA led to the compromise of two Apache Software Foundation servers. The JIRA password database was compromised. The database contained unsalted password hashes, which are vulnerable to dictionary lookups and cracking tools. Apache advised users to change their passwords. Atlassian themselves were also targeted as part of the same attack and admitted that a legacy database with passwords stored in plain text had been compromised.
- "About Atlassian – customers, life, community, FedEx days". Atlassian. Retrieved 27 February 2012.
- Atlassian. "ATLASSIAN – Open Source Project License Request". Atlassian.com. Retrieved 9 November 2012.
- Atlassian. "ATLASSIAN – Community License Request". Atlassian.com. Retrieved 9 November 2012.
- "How is JIRA pronounced?". Retrieved 17 March 2010.
- "What does JIRA mean?". Retrieved 16 March 2012.
- "JIRA RPC Services – JIRA Development". Developer.atlassian.com. 21 October 2011. Retrieved 3 January 2012.
- "Subversion JIRA plugin". Studio.plugins.atlassian.com. 18 July 2012. Retrieved 23 July 2012.
- "Jira Integrating with a Source Control System".
- "Choosing a Default Language". confluence.atlassian.com. Retrieved 13 October 2011.
- "Atlassian.org". Retrieved 9 July 2013.
- "Bug Tracker – Second Life Wiki". Wiki.secondlife.com. 5 September 2011. Retrieved 15 September 2011.
- "Springframework.org". Jira.springframework.org. Retrieved 15 September 2011.
- "Atlassian.com". Opensource.atlassian.com. Retrieved 15 September 2011.
- "Fedora Repository Project". DuraSpace. Retrieved 28 January 2014.
- "Skype.com". Developer.skype.com. Retrieved 15 September 2011.
- "Apache.org". Issues.apache.org. Retrieved 15 September 2011.
- "ApacheJira". Retrieved 25 September 2008.
- "JIRA: Licensing and Pricing". Atlassian. Retrieved 10 July 2011.
- Golucci, Philip (13 April 2010). "apache.org incident report for 04/09/2010". The Apache Software Foundation. The Apache Infrastructure team. Retrieved 29 May 2013.
- Cannon-Brookes, Mike (13 April 2010). "Oh man, what a day! An update on our security breach". Atlassian Blogs. Atlassian. Retrieved 29 May 2013.