Skip to main content
TrustRadius
Jira Software

Jira Software

Overview

What is Jira Software?

JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the…

Read more
Recent Reviews

Jira is a Saviour

9 out of 10
March 08, 2024
Incentivized
Jira Software is a project management tool that is widely used by various teams in our organization to manage their projects and tasks. …
Continue reading

TrustRadius Insights

Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Standard

$7

Cloud
Per User Per Month

Premium

$14

Cloud
Per User Per Month

Free

Free

Cloud

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.atlassian.com/software/jira…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $10 per month
Return to navigation

Product Demos

JIRA Project Management Tutorial for Beginners (2022)

YouTube

The full overview: Roadmaps in Jira Software

YouTube
Return to navigation

Product Details

What is Jira Software?

Jira Software is a software development tool used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects from a single tool, helping teams release higher quality software, faster.

And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.

With Jira Software, teams are able to:

  • Track versions, features, and progress at a glance
  • Easily re-prioritize user stories and bugs
  • Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
  • Estimate, track and report on story points; become more accurate
  • Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
  • Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
  • Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
  • Flexibly tailor Jira tasks and their workflows to a specific team's use case
  • Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default

Jira Software Videos

Jira in a Nutshell Demo Video
Jira Software is a software development project management tool of sorts, that tracks progress, offers up project reports, and gives a great roadmap view to understand workloads and deadlines better. In this video, the TrustRadius team goes over Jira Software pricing, top feat...
 Show More

Jira Software Competitors

Jira Software Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Mac
Mobile ApplicationApple iOS, Android

Frequently Asked Questions

JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.

Jira Software starts at $10.

Bugzilla, Podio, and Zoho Projects are common alternatives for Jira Software.

Reviewers rate Support Rating highest, with a score of 8.8.

The most common users of Jira Software are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(3250)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.

Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.

Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.

Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.

Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.

Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.

Attribute Ratings

Reviews

(1-5 of 5)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Project management. The tickets for a development and testing are mapped as a Jira Software story,easy to track , segment and comment.
  • Ticket management
  • Defect management
  • Business process management
  • Effective communication between cross functional teams
  • Easy to use
  • Project management
  • Interactive UI
  • Could be a room for improvement towards documents upload and tracking
  • More info of the linked ticket
  • Could have better UI
  • Load time could be enhanced
  • Sometimes document upload fails
Suited for long term projects.

Where the team size is big and volume of tickets more.

It is less appropriate we are the team size is less and and the ticket could be solved by an excel sheet itself because there is a cost involved as well as it is not free
  • Process workflow
  • Team collaboration
  • Effective Agile and Scrum management tool
  • Effective tool for issue management
  • Difficult to track project progress
  • Enhanced team collaboration
  • Provides custom workflow for the freshers to understand the QA flow
  • Difficult for non techy people
  • Rally
It's ability to handle issue management and ticket.

  • Task management
  • Issue management
  • Team collaboration
  • Track project progress
  • Customize
  • Educate non techy person
Yes, but I don't use it
Lisandro Fernigrini | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Jira was implemented to track all Product development, customizations, and customer production support tasks in the Argentina solution center. Product development teams keep track of user stories, development tasks, and test cases, while product support attending customers keeps track of bugs or product enhancements, using a single tool that also integrates with other internal/legacy tools.
  • Very customizable, workflows can be defined based on company definitions.
  • Improves communication and access to information. It is easy to understand each item's status, priority, and responsible person.
  • Allows us to prioritize tasks and estimate delivery dates.
  • May have too many options for small and simple projects, making it a little hard to use for starter users.
  • It is more expensive that other options.
  • Help does not cover all options.
It is great to manage a software center or big development teams. It includes all options that are usually needed to manage the product development cycle and it has many customization/configuration options that allow it to adapt to your organization's processes. It is a little too complex for small teams and the effort to customize it may be too much compared with other less complete but still acceptable solutions.
  • Integration with other tools (Confluence, etc.).
  • Ability to customize and configure workflows and rules.
  • Easy filtering options.
  • Adaptable to most frequent used agile methodologies.
  • Unified development and support tasks in a single tool.
  • Collaboration between teams.
  • Quicker response times and better visibility of tasks status.
I personally use Trello to keep track of personal stuff and used it as a task management tool for very small development teams/projects, but Jira is a million miles ahead of it regarding a number of options and customizations. I also used Rally on a previous company and although it is a quite complete tool I think Jira offers more options, mostly regarding customizations.
200
All Engineering and Management Team members use the tool, from Senior Management (use dashboard to analyze project status), Product Managers (define and prioritize development tasks), and development team members (Software Architects, Software Developers, and Testers) to develop and test features, track and solve defects and request and develop product enhancements.
  • Manage workload
  • Prioritize tasks and resource assignment.
  • Reduce delivery time.
Without taking into account pricing (I do not know the details but it is more expensive than other options) the product allows us to design, develop and deliver software products in a simpler, more integrated, and visible way. Information and status about tasks, enhancements, and bugs are easily available for all members of the organization.
The software is quite easy to use once you get used to it. Some effort is required to configure and customize options and workflows, but once everything is set up as desired and you get used to the tool it delivers what is expected.
  • Advanced search
  • Stories creation
  • Time tracking
  • Attaching big files
Yes, but I don't use it
Score 8 out of 10
Vetted Review
Verified User
Incentivized
The use of JIRA is company-wide but sporadically. JIRA is viewed as an "opt-in" tool in our organization and is mainly sought by the development groups. We have had some success pushing it out to business users in departments that would benefit from ticketing and tracking of workload. In general, development and QA are the primary users.
  • Differentiated workflows. It was important to us that new product development could be handled differently than IT implementation bugs, etc., and JIRA does a great job of allowing us to treat efforts appropriately without a lot of complicating customization.
  • Card view. The layout of the work items on the board is user friendly and easily gives the team a handle on what is happening during the working period. The drag and drop functionality is constantly lauded by our teams and whenever alternate tools are reviewed, is one of the top features used for comparison.
  • Simplified Querying. One of the biggest selling points to the business groups that have taken on JIRA is that finding items in the system doesn't depend on someone with say, SQL talents. Though there are complaints on querying more complicated information from some, overall the WYSIWYG interface for querying tickets is very helpful for business users to "self-service" information.
  • Integration with wiki tool (Confluence). This I think is one of the biggest draws for us on the business side. We find that JIRA is sometimes too complicated for the business user and were able to build dashboards and pages that help the business users navigate to what they need to know. Being able to maintain up-to-date reporting from JIRA without having to constantly update is beyond valuable.
  • Reporting. JIRA has always been a little finicky on the reporting side in my opinion. The gadgets are helpful but can be confusing if you aren't shown how to use them. Time tracking continues to get worse rather than better with the removal of the one built-in timesheet we had replaced by a paid plugin with fewer options.
  • Roles Based Permissions. JIRA is really light on this but you can work it out using validations in the workflows and permission schemes. I think this is not intuitive for most admins and they wind up with a very unrestricted instance of the tool. Sometimes setup can be a pain because of the openness.
  • Ramp up is long. JIRA is really difficult to understand and to be properly configured if it doesn’t suit you out of the box. Once you understand all the ins and outs of the setup process you can wind up with a decent tool but it's the fact that you need someone to sit there and learn it before you can use it - not a coherent message to management when pitching Agile.
  • Or to some "missing features". Some features that the community feels should be a part of the core product are only available via plugin. Again, the message to management when trying to purchase these is disconcerting to leaders that are used to the "big box, all in one, everything you need, one price" solutions.
  • Business Features. Depending on your final configuration you may find tracking business features rather onerous. Based on release structure we have a non-traditional setup where our business projects exist in one space with children work in software spaces. It is the easiest solution to our technical release issues. There is only one ticket type that can have children spanning projects and it is the Epic. Pulling in children tickets is time-consuming and laborious. I discovered that I could automate update of a ticket field on children tickets to help tracking back but it's not elegant and is open to creating gaps should things change (and they often do in Cloud JIRA).
JIRA is a great tool for developers or business user with the cognitive abilities to build ticket searches. It allows users to manage work within Scrum principles and provides easy to use interfaces for the technically inclined. If your user base is broad and you need to allow for differing treatment of work tickets JIRA is a good tool. I think JIRA is simply too overwhelming for some teams, providing a vast array of features that are not required. For those teams something simpler might be a better fit. I also think that business users that are not technically inclined will experience a long ramp up and might even defect (if allowed) out of frustration without a mentor.
  • Positive: this tool provides a convenient and efficient workspace for our developers/QAs as well as transparency for our leaders in the Dev/QA space. Higher level tracking (at the Epic) level gives greater transparency at the business feature level but could be improved.
  • Negative: this tool requires a lot of time to learn and maintain. Updates are not always clear in their impact so you do accept (even in a Cloud situation) that if you do not use JIRA with no modifications (I have never heard of this by the way) you will need someone to keep an eye on it. Consider it to be 25% to 50% of a headcount based on your configuration complexity.
We remain with JIRA even though our umbrella company is fully invested with ServiceNow(SNOW) as SNOW has just a portion of the utility of JIRA when it comes to agile development. SNOW also requires advanced technicians and an entire support team to maintain, whereas JIRA's cloud structure allows a team of 3 maintain most functions here. Our umbrella company is also invested with Workfront in the creative/marketing area, again, there are key functions like the scrum planning and though the reporting appears to be superior, there is a fair amount of manual interaction required to keep it up to date - much more for our purposes that is automatic in JIRA.
No
I don't know that it is offered for JIRA - we do have quicker service based on our impacted users which tends to be large.
Whenever I contact the support staff at JIRA I find the interaction to be typical to support interactions. Quite a few of the staff are very friendly and always seem to want to help. I have given them a couple tough situations that they've had to take back but all-in-all it seems like they try very hard to get to the root of the problem in a timely manner.
Yes
I think the term "bug" might be the wrong label. We had a misaligned update. Since we are on the Cloud and the releases are managed by Atlassian we encounter situations where our instance is part of that 1% customization that breaks when the release goes out. We routinely inquire as to how to maintain certain functionality and often find it has been updated and we simply need to update our approach.
None spring to mind at the time of this writing but I have very positive impressions of the support team at Atlassian.
  • Prioritization for Stories, etc is very nimble; caveat for the issuetype "Epic" which is decidedly less so.
  • Sprint planning
  • WYSIWYG query tool
  • Dashboard gadgets for Agile development tracking
  • Feature prioritization (at the Epic level for our shop) is very hard to use in the Backlog - we've developed a hack where we prioritize Epics in a Kanban board but it's got an element of disconnect to the Backlog planning that isn't very "agile"
  • Portfolio tracking - you might try to arrange features according to Business Goals but you'd have to 1) purchase the Portfolio tool from Atlassian which is the same price as the JIRA Software itself or 2) build and maintain insane filters
  • Time tracking - your time tracking will again be a choice between purchasing a plugin that does half of what you want or maintaining JQL that does backflips for the same level of value
Yes, but I don't use it
I think JIRA has a lot of complexity for a less technical user and I am torn between whether that is an essential problem. I tend to believe that users should choose the tool that fits the work; this means does it make sense for the typical user and how much integration with other systems does it provide? If both of these things are high, I would say the tool deserves high consideration. As a technical tool I think JIRA falls squarely in line with technical expectations - it also provides a high degree of integration possibilities with other tools. I suppose if you were forced to choose one tool you should plan on a staggered approach to rolling it out, starting with the technical team guided by someone with a process background.
March 08, 2016

I'm a fan!

Tracy Walton | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized
JIRA was used by our software development organization as the one true source for what work needed to be done, when and by whom. Although our approach was generally waterfall with some agile-esque concepts mixed in, JIRA proved to be a powerful tool for us. We created an extensive JIRA workflow to track and manage portions of our development projects from idea, design & requirements, development, QA, tech writing, UAT, etc. We also made extensive use of the dashboards to provide transparency to individual contributors and stakeholders alike.
  • The biggest impact from experience with JIRA is the transformation it took from when I first started using it, until now. It seemed like the good folks at JIRA really practiced what they preached and I reaped the benefits. When I first started using the agile boards, it was at a time when they had just come out with a new version if you will and were sunsetting the old version (I can't remember the names). Anyhow, the agile board worked enough for me to check the box that I had a backlog. It did the basics. As time went on however, I was thoroughly impressed at the features that they added. It was as if they had been sitting at my desk alongside me and noticing my frustrations and then fixing them.
  • Other favorite features, dashboards, saved searches, workflow, labels, advanced search query, linked issues, follow issue, history, batch updates, view in issue navigator. All these features seriously make life easier when working in JIRA. The administrative headaches of product management are out the window.
  • I also dig the administrative features like find my field. This makes it so easy for an administrator to identify the cause of a configuration error and fix/test quickly.
  • One thing that ever bothered me about JIRA was the rank feature. It used to be a global rank, so I could I query issues and display them in results by order of priority (rank) regardless of what sprint they were in. Now rank is only applicable in the context of a sprint, which is not so powerful really if I want to prioritize across several teams regardless of sprint.
  • It would be nice to batch update labels, and not have the "all or nothing" approach. At least they have keyboard shortcuts that make updating many issues one at a time a total breeze.
  • At my new company, I'm having a hard time converting my peers and management into JIRA admirers. Their concerns are mainly the price and the ease in which the system can be integrated into our homegrown system. Can you make some sort of browser plugin that could compare how long it takes me to complete the same work in JIRA vs my current application?
Not sure if a smaller organization would really use all the bells and whistles that JIRA offers. Trello could be a good alternative to get started with, but my guess is that as you grow you'll benefit from an industry standard like JIRA - good thing they make it easy to import your issues from other systems.
  • As a product manager I needed to make sure that all teams were aware of priority and that new items went through triage and were accounted for in a timely manner. JIRA took us away from the headache of spreadsheets and daily meetings, to one transparent system with real time dashboards that required no meetings. People could just do their work because they knew what was the next most important item. This must have saved hundreds of thousands of hours over the years.
I was not part of the team who decided to go with JIRA, however I have used Rally, Trello and spreadsheets and JIRA beats them all hands down. Rally was a good starter system, but they did not (at least at the time) have the advanced query and administrative/configuration features that JIRA has. Trello is a good team tool as well, but lacks a true backlog feature as well as advanced queries. Spreadsheets are great if nothing changes, so...
  • keyboard shortcuts are amazing and same so much time
  • Find my field is an amazing feature that also takes me to the correct admin config for me to make the updates I want so that I don't have to hunt around for what I'm looking for.
  • The advanced search and saved searches make finding the issues important to me very easy. Nothing falls through the cracks.
  • Managing labels across the system can be tough. It can get ugly if you have a lot of people using them and one person uses a capitol and someone doesn't. Then your searches need to include all permutations of the label to make sure you get the results of issues you're looking for.
  • Configuration can be a bit daunting, but the Atlassian university was a great help.
Yes, but I don't use it
I would give it a 10 but it doesn't read my mind yet.
October 06, 2014

Atlassian JIRA

Score 9 out of 10
Vetted Review
Verified User
Atlassian JIRA is used by some sections within the organisation. It is mainly used by IT for managing project work and workloads. It is also used to keep track of feature requests for a piece of software we have had externally developed for us. We are currently piloting the use of Service Desk for one of our business units.
  • Easy to use and configure.
  • Provides visibility of workloads.
  • Provides visibility and tracking of progress against certain tasks.
  • Allows you to go back and track historical decisions.
  • Good roadmap, existing and new features always being worked on.
  • Within the Agile area it would be nice to be able to track versions more easily, whilst it does it I don't find this area all that intuitive.
Atlassian JIRA is useful for scenarios where you need to track issues or tasks and record updates or progress against them. We have set up projects for a couple of different areas within our organisation, from service based areas, to areas that need basic incident tracking to IT where we use it to track project work and feature requests.
  • From an IT perspective this allows us to make sure we are managing workloads and due dates effectively.
  • From an organisational perspective it provides us with a tool we can use to track issues and tasks, with minimal setup overheads and minimal training. It is also very configurable, allowing us to configure JIRA to match business processes rather than needing to change business processes to match JIRA.
Atlassian JIRA is really working for us, and we can see many other areas of the organisation where its use could be applied to streamline service.
  • Adding new issues
  • Tracking progress and recording comments against an issue
  • Assigning issues to employees so they are responsible
Yes, but I don't use it
In our experience users have required little or no training to get up and running with this product.
Return to navigation