Wikipedia

User:MistermindOlaf/Jira Software

Developer(s)Atlassian[1]
Initial release2002; 22 years ago (2002)[2]
Written inJava
Operating systemCross-platform
TypeIssue tracking system, bug tracking system, project management software
LicenseProprietary
Websitewww.atlassian.com/software/jira

Jira (/ˈdʒiːrə/ JEE-rə)[3] Software is a commercial proprietary issue tracking product developed by Atlassian that implements agile methodologies for software development teams.[4] Jira Software is used for various purposes such as project management, issue tracking, requirements management and bug tracking. Jira Software evolved from Jira which started as bug tracking software and later split into multiple products to support issue tracking in many different organizations.[4]

Use cases of Jira Software include Requirements and Test Case Management, Agile Team Management, Project Management, Software Development, DevOps, Product Management and Task Management.

Naming edit

The product name comes from the second and third syllables of the Japanese word pronounced as Gojira, which is Japanese for Godzilla.[5] The name originated from a nickname Atlassian developers used to refer to Bugzilla, which was previously used internally for bug-tracking.[5]

History edit

 
Timeline representing the split of JIRA into Service Desk, Core and Software.

When launched in 2002, Jira was purely bug tracking software, targeted at software developers. The app was later adopted by non-IT organizations as a project management tool. The process sped up after the launch of Atlassian Marketplace in 2012, which allowed third-party developers to offer project management plugins for Jira.[6] BigPicture, Advanced Roadmaps (formerly Portfolio), Structure, Tempo Planner and ActivityTimeline[7][8] are major project management plugins for Jira.[9] In 2015, Jira split into three separate standalone products with JIRA Software focusing on agile software development teams.[10] In 2017, JIRA was renamed to Jira, changing the name of JIRA Software along with it.[11]

Description edit

Jira Software is a project management and issue tracking tool designed for software development teams. It supports agile development methodologies and provides a variety of features such as task assignment and tracking, reporting, and integration with other tools. It helps software development teams to plan, track, and release their software efficiently.[12]

Usages edit

Jira Software is a work management tool that is intended to aid various types of teams in managing their work. Originally, Jira was designed as a bug and issue tracker but has evolved into a powerful tool for various use cases[13]. It is used by over 65.000 companies globally.[14]

Use cases include:

Requirements and Test Case Management edit

One possible use case for Jira Software is requirements[15] and test case management. It can be utilized as a central hub for teams that develop software incrementally, and it can integrate with various add-ons for test management. This allows for the seamless integration of quality assurance testing into the software development process. Users can utilize Jira issues, custom screens, fields, and workflows to manage manual and automated tests, resulting in effective and incremental testing and higher quality final products.[13][14]

An industrial case study was conducted, in which Jira and third-party plugins were used for requirements management and traceability in the field of transit systems. The study describes how Jira can be configured and customized to effectively manage and track requirements, and how third-party plugins can be used to generate traceability reports. The study suggests that Jira, being low-cost and easy to use, is a viable option for requirements management for small and medium-sized enterprises as well as larger corporations despite not being specifically designed for requirement management.[16]

The study mentions several features of Jira that enables its use for requirements management. It explains that Jira issues can represent requirements, can be characterized with custom fields and tracked using logging capabilities of Jira. The existing issue types Stories and Epics can be used for this purpose.[17][18][19] Additionally, the industrial case study mentions links as a way to enable traceability between items. Furthermore, it identifies dashboards and reports as aids in managing requirement prioritization. However, it also identifies properly textually describing requirements as problematic in Jira, as descriptions can only be created in a basic text window. It agrees with Atlassian[20] that integration with Confluence solves that. Both the industrial case study and Atlassian also promote third-party add-ons in the Atlassian Marketplace which extend functionality with for example branching, traceability matrices, viewers, diagrams, auditing and reports.[21][22][23] Some of these third-party add-ons are RTM[24], R4J[25] and RMsis[26]. Furthermore, some requirement management vendors have also integrated their tools with Jira. Examples are eazyBI[27], HelixRM[28] and ReqView[29]. Lastly, it is good to note that user role modeling and persona support as well as customer collaboration are not supported by Jira Software according to respondents from a 2018 survey.[15]

Agile Team Management edit

Another common use case is Agile team management.[30][31][32] For teams that use agile methodologies, Jira Software provides Scrum and Kanban boards as standard features. These boards act as task management hubs, where tasks are mapped to customizable workflows, providing transparency and visibility into the status of each work item. The software also includes time tracking capabilities and real-time performance reports such as burn-up/down charts, sprint reports, and velocity charts, allowing teams to closely monitor their productivity over time. Jira Software supports any agile methodology for software development.[13][14]

Project Management edit

Jira Software can also be used for project management. Teams can begin with a project template or create their own custom workflow. Jira issues track each piece of work that needs to pass through the workflow steps to completion. Customizable permissions allow administrators to determine who can see and perform specific actions. With all project information in one place, progress, productivity, and oversight can be tracked through generated reports.[13][14]

Software Development edit

The software can also assist in software development, providing planning and roadmap tools for teams to manage stakeholders, budgets, and feature requirements from the start. Jira Software can be used throughout every stage of the software development lifecycle, from initial ideation to deploying new features to customers and all of the many steps in between. The Jira board serves as the central hub for all work related to a specific project, and with strategic apps and integrations, relevant data can be seamlessly integrated into Jira.[13][14]

One paper discusses the use of the JIRA issue tracking system from Atlassian at the National Ignition Facility (NIF) for managing software development projects. The NIF has been using JIRA actively for 63 different projects, creating over 80,000 requests for new features and bug fixes. The paper details how JIRA has been customized to meet the specific needs of the NIF's software development process, including the creation of a custom workflow for tracking code reviews, recording test results from both developers and the quality control team, and managing product releases. It also explains how JIRA's advanced customization capabilities have been used to track key metrics about the ICCS development effort, such as developer workload.[33]

DevOps edit

DevOps teams can also utilize Jira Software as it serves as the backbone of Atlassian’s open and integrated toolchain, Open DevOps. The software integrates with various first- and third-party tools throughout the DevOps life cycle, including code and version control tools, documentation and knowledge management tools, and monitoring and operating tools. This allows DevOps teams to efficiently ship better software by focusing on best practices such as automation, testing, security, observability, feature flagging and continuous delivery and deployment.[13][14]

Product Management edit

Jira Software can be used for product management, enabling teams to build roadmaps that are associated with each project. The roadmap allows teams to outline the longer-term view of their work and track progress and share progress with others. More detail can be added to the roadmaps, showing dependencies and forecasts for when they might complete their work, and teams can create a view highlighting live roadmaps from multiple teams by embedding the Jira Software roadmap into Confluence.[13][14]

Task Management edit

Jira Software can be used for task management for individuals and teams, allowing for tasks to be created with details, due dates, and reminders, and for others to watch and track progress and be notified when the task is completed.[13][14]

License edit

Jira Software is a commercial software product and is available in three different license types: Data Center, Cloud and Server.[34]

Architecture edit

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 (RPCs), Jira has REST, SOAP, and XML-RPC interfaces.[35] Jira integrates with source control programs such as Clearcase, Concurrent Versions System (CVS), Git, Mercurial, Perforce,[36] Subversion,[37] and Team Foundation Server. It ships with various translations including English, French, German, Japanese, and Spanish.[38]

Jira implements the Networked Help Desk API for sharing customer support tickets with other issue tracking systems.[39]

See also edit

References edit

  1. ^ "Jira". Atlassian.com. Retrieved 8 September 2020.
  2. ^ "About us". Atlassian.com official website. Retrieved 27 February 2012.
  3. ^ "How is JIRA pronounced?". Atlassian.com official website. Retrieved 8 April 2019.
  4. ^ a b Li, Patrick (2019). JIRA 8 essentials : effective issue management and project tracking with the latest Jira features (5th ed.). Birmingham, UK: Packt. p. 8. ISBN 1-78980-819-7. OCLC 1098198099.{{cite book}}: CS1 maint: date and year (link)
  5. ^ a b "What does JIRA mean?". Atlassian.com official website. Retrieved 5 November 2019.
  6. ^ "Atlassian Launches A Marketplace For Project Management Add-Ons – TechCrunch". techcrunch.com. Retrieved 2 July 2018.
  7. ^ "Resource Planning in Jira: Top 7 apps on the Marketplace". Reliex. 12 February 2020. Retrieved 28 October 2021.
  8. ^ "Resource Planning & Timesheets for Jira | ActivityTimeline". activitytimeline.com. Retrieved 16 August 2022.
  9. ^ "Jira Project Management Tool. Compare "big 4" | SoftwarePlant". SoftwarePlant.com. 24 March 2018. Retrieved 2 July 2018.
  10. ^ Lardinois, Frederic (6 October 2015). "Atlassian Splits Its JIRA Project Tracking Service Into 3 Standalone Offerings To Better Serve Non-Technical Teams". TechCrunch. Retrieved 10 January 2023.
  11. ^ "Is it "JIRA" or "Jira"?". Atlassian Community. 30 November 2017. Retrieved 11 January 2023.
  12. ^ Atlassian. "Jira Overview | Products, Projects and Hosting". Atlassian. Retrieved 11 January 2023.
  13. ^ a b c d e f g h Atlassian. "Who uses Jira?". Atlassian. Retrieved 10 January 2023.
  14. ^ a b c d e f g h Atlassian. "What is Jira Software used for?". Atlassian. Retrieved 10 January 2023.
  15. ^ a b Gaikwad, Vandana; Joeg, Prasanna; Joshi, Shashank (2018), Silhavy, Radek; Silhavy, Petr; Prokopova, Zdenka (eds.), "AgileRE: Agile Requirements Management Tool", Cybernetics Approaches in Intelligent Systems, vol. 661, Cham: Springer International Publishing, pp. 236–249, doi:10.1007/978-3-319-67618-0_22, ISBN 978-3-319-67617-3, retrieved 24 January 2023
  16. ^ Filion, Luc; Daviot, Nicolas; Le Bel, Jean-Philippe; Gagnon, Marc (2017). "Using Atlassian tools for efficient requirements management: An industrial case study". 2017 Annual IEEE International Systems Conference (SysCon). Montreal, QC, Canada: IEEE: 1–6. doi:10.1109/SYSCON.2017.7934769. ISBN 978-1-5090-4623-2.
  17. ^ s.r.o, Eccam (16 November 2021). "Requirements Management for Jira". www.reqview.com. Retrieved 11 January 2023.
  18. ^ Harned, David (2018). Hands-On Agile Software Development with JIRA : Design and Manage Software Projects Using the Agile Methodology. Birmingham: Packt Publishing Ltd. pp. 31–32. ISBN 978-1-78953-962-2. OCLC 1080999209.
  19. ^ Atlassian. "Epics, Stories, Themes, and Initiatives". Atlassian. Retrieved 11 January 2023.
  20. ^ "Using Jira for Requirements Management | Jira | Atlassian Documentation". confluence.atlassian.com. Retrieved 11 January 2023.
  21. ^ Filion, Luc; Daviot, Nicolas; Le Bel, Jean-Philippe; Gagnon, Marc (2017). "Using Atlassian tools for efficient requirements management: An industrial case study". 2017 Annual IEEE International Systems Conference (SysCon). Montreal, QC, Canada: IEEE: 2. doi:10.1109/SYSCON.2017.7934769. ISBN 978-1-5090-4623-2.
  22. ^ "Using Jira for Requirements Management | Jira | Atlassian Documentation". confluence.atlassian.com. Retrieved 11 January 2023.
  23. ^ "Requirements management: 6 best practices". Atlassian Community. 5 March 2018. Retrieved 11 January 2023.
  24. ^ "Requirements & Test Management for Jira". Atlassian Marketplace. Retrieved 11 January 2023.
  25. ^ "R4J - Requirements Management for Jira". Atlassian Marketplace. Retrieved 11 January 2023.
  26. ^ "RMsis - Requirements Management for Jira". Atlassian Marketplace. Retrieved 11 January 2023.
  27. ^ "eazyBI | Easy Business Intelligence for Project Teams". eazyBI. Retrieved 11 January 2023.
  28. ^ "Helix Requirements Management | Perforce". www.perforce.com. Retrieved 11 January 2023.
  29. ^ s.r.o, Eccam. "Requirements Management Tool for HW/SW Systems | ReqView". reqview.com. Retrieved 11 January 2023.
  30. ^ Raith, Florian; Richter, Ingo; Lindermeier, Robert (2017). "How Project-management-tools are used in Agile Practice: Benefits, Drawbacks and Potentials". Proceedings of the 21st International Database Engineering & Applications Symposium on - IDEAS 2017. Bristol, United Kingdom: ACM Press: 30–39. doi:10.1145/3105831.3105865. ISBN 978-1-4503-5220-8.
  31. ^ Özkan, Deniz; Mishra, Alok (1 November 2019). "Agile Project Management Tools: A Brief Comprative View". Cybernetics and Information Technologies. 19 (4): 17–25. doi:10.2478/cait-2019-0033. ISSN 1314-4081.
  32. ^ Matta, Martina; Marchesi, Michele (2015). "Understanding Approval Rating of Agile Project Management Tools using Twitter". 10th International Conference on Software Engineering and Applications: 168–173. doi:10.5220/0005557201680173. ISBN 978-989-758-114-4.
  33. ^ Fisher, J.; Koning, D.; Ludwigsen, A. P. (16 September 2013). "Utilizing Atlassian Jira For Large-Scale Software Development Management*". {{cite journal}}: Cite journal requires |journal= (help)
  34. ^ Atlassian. "Jira Software Licensing". Atlassian. Retrieved 23 January 2023.
  35. ^ "JIRA RPC Services". Atlassian.com official website. 21 October 2011. Retrieved 3 January 2012.
  36. ^ "Integrating with Development Tools". Atlassian.com official website.
  37. ^ "Subversion JIRA plugin". Atlassian.com official website. 18 July 2012. Archived from the original on 27 January 2013. Retrieved 23 July 2012.
  38. ^ "Choosing a Default Language". Atlassian.com official website. Retrieved 13 October 2011.
  39. ^ Latkiewicz, Matthew (7 June 2011). "Zendesk's JIRA Integration Rocks!". Retrieved 6 May 2016.

External links edit

Category:2002 software Category:Atlassian products Category:Bug and issue tracking software Category:Java (programming language) software Category:Project management software Category:Task management software


Retrieved from "https://en.wikipedia.org/w/index.php?title=User:MistermindOlaf/Jira_Software&oldid=1135414664"