From Wikipedia, the free encyclopedia
  (Redirected from JIRA (software))
Jump to: navigation, search
This article is about the software-engineering package. For other uses, see Jira.
JIRA logo.svg
JIRA logo
Developer(s) Atlassian, Inc.
Initial release 2002; 13 years ago (2002)[1]
Stable release 6.4 / March 17, 2015; 8 months ago (2015-03-17)[2]
Written in Java
Operating system Cross-platform
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[3][4]
Website atlassian.com/software/jira

JIRA (/ˈi.rə/ JEE-rə)[5] 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,[6] itself a reference to JIRA's main competitor, Bugzilla. It has been developed since 2002.[1]


According to Atlassian, JIRA is used for issue tracking and project management by over 25,000 customers in 122 countries around the globe.[7] Some of the organizations using JIRA for bug-tracking and project management are Fedora Commons,[8] Hibernate,[9] Honeywell Aerospace,[10][not in citation given] JBoss,[11] Linden Lab,[12][not in citation given] Skype,[13] Spring Framework,[14] and The Apache Software Foundation uses JIRA and Bugzilla.[15] JIRA includes tools allowing migration from competitor Bugzilla.[16]

Compared to Bugzilla, JIRA is more internally customisable. Bugzilla has a single, fixed, state machine to represent the lifecycle of a 'bug'. All such bugs are assumed to follow the same fixed pattern of detection, repair and test. All bugs must also have the same lifecycle. JIRA allows this state machine to be changed by its users, and also for different classes of issue to be tracked, each with their own state machine. This makes JIRA far more flexible: it may be used as a more general "issue tracker" rather than solely a bug tracker, tracking new feature requests, system admin tasks, Scrum tasks or any other feature that its users might require. To avoid the overhead of configuring JIRA for each new task type, pre-built configurations such as GreenHopper (now JIRA Agile[17]) can be bought-in, which provide a pre-configured JIRA environment with tasks and behaviours appropriate for popular management methodologies.[18]

JIRA is now[when?] offered in three packages:[citation needed]

  • JIRA Core includes the base software.
  • JIRA Software is intended for use by software development teams and includes JIRA Core and JIRA Agile.
  • JIRA Service Desk is intended for use by IT or business service desks.

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 REST, SOAP, and XML-RPC.[19] JIRA integrates with source control programs such as Clearcase, Concurrent Versions System (CVS), Git, Mercurial, Perforce,[20] Subversion,[21] and Team Foundation Server. It ships with various translations including English, French, German, Japanese, and Spanish.[22]

The main featues of JIRA for agile software development are the functionality to plan development iterations, the iteration reports and the bug tracking functionality (A JIRA Bug is usually abbreviated to JB).


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.[23]

Atlassian provides JIRA for free to open source projects meeting certain criteria, and to organizations that are non-academic, non-commercial, non-governmental, non-political, non-profit, and secular. For academic and commercial customers, the full source code is available under a developer source license.[23]


In April 2010 a cross-site scripting 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.[24] 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.[25]

See also[edit]


  1. ^ a b "Atlassian – About us". Atlassian. Retrieved 27 February 2012. 
  2. ^ "Release Summary". Atlassian. Retrieved 19 March 2015. 
  3. ^ Atlassian. "ATLASSIAN – Open Source Project License Request". Atlassian.com. Retrieved 9 November 2012. 
  4. ^ Atlassian. "ATLASSIAN – Community License Request". Atlassian.com. Retrieved 9 November 2012. 
  5. ^ "How is JIRA pronounced?". Retrieved 17 March 2010. 
  6. ^ "What does JIRA mean?". Retrieved 16 March 2012. 
  7. ^ "Atlassian.org". Retrieved 9 July 2013. 
  8. ^ "Fedora Repository Project". DuraSpace. Retrieved 28 January 2014. 
  9. ^ "Atlassian.com". Opensource.atlassian.com. Retrieved 15 September 2011. 
  10. ^ [1]/
  11. ^ Jboss.org/
  12. ^ "Bug Tracker – Second Life Wiki". Wiki.secondlife.com. 5 September 2011. Retrieved 15 September 2011. 
  13. ^ "Skype.com". Developer.skype.com. Retrieved 15 September 2011. [dead link]
  14. ^ "Springframework.org". Jira.springframework.org. Retrieved 15 September 2011. 
  15. ^ "Apache.org". Issues.apache.org. Retrieved 15 September 2011. 
  16. ^ "ApacheJira". Retrieved 25 September 2008. 
  17. ^ "Say "hello" to JIRA Agile and JIRA Capture". Atlassian. August 26, 2013. 
  18. ^ "JIRA Agile". Atlassian. 
  19. ^ "JIRA RPC Services – JIRA Development". Developer.atlassian.com. 21 October 2011. Retrieved 3 January 2012. 
  20. ^ "Jira Integrating with a Source Control System". 
  21. ^ "Subversion JIRA plugin". Studio.plugins.atlassian.com. 18 July 2012. Retrieved 23 July 2012. 
  22. ^ "Choosing a Default Language". confluence.atlassian.com. Retrieved 13 October 2011. 
  23. ^ a b "JIRA: Licensing and Pricing". Atlassian. Retrieved 10 July 2011. 
  24. ^ 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. 
  25. ^ Cannon-Brookes, Mike (13 April 2010). "Oh man, what a day! An update on our security breach". Atlassian Blogs. Atlassian. Retrieved 29 May 2013. 

External links[edit]