Jira is a Saviour
Jira Software is a project management tool that is widely used by various teams in our organization to manage their projects and tasks. …
Starting at $81.85 per month 10 users
View PricingOverview
What is Jira Software?
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Recent 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
Pricing
Standard
$8.15
Cloud
per month per user (minimum 10)
Premium
$16
Cloud
per month per user (minimum 10)
Data Center
$44,000
On Premise
per year 500 users
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)
- $81.85 per month 10 users
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
YouTube
The full overview: Roadmaps in Jira Software
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a project management tool software 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. 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.
Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- 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 Integrations
Jira Software Competitors
Jira Software Technical Details
| Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Windows, Mac |
| Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.
Jira Software starts at $81.85.
Reviewers rate Support Rating highest, with a score of 8.8.
The most common users of Jira Software are from Enterprises (1,001+ employees).
Comparisons
Compare with
Reviews and Ratings
(3242)
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!
- Pros
- Cons
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-2 of 2)Companies can't remove reviews or game the system. Here's why
February 27, 2018
Jira- Effective Tool to manage Agile Teams
It is being used at a program level in the organisation. We use JIRA to track our Agile teams that are [composed] of Scrum and Kanban teams. We use it for tracking epics, stories, issues, tasks, subtasks, production maintenance tracking, and planning.
It provides a good dashboard where higher leadership can look at how things are progressing and ultimately bringing in transparency.
It eliminates the need for individual teams to send weekly or monthly status reports to leadership on progress and what they are involved with. So at team level sprints, stories, epics, sizing, capacity, scrum and Kanban boards are managed and looked at.
- Requirements are managed very well there which can be captured in the form of epics.
- Epics, which capture the high-level ideas can be broken down into stories, tasks and sub-tasks.
- The team can team can raise bugs, capture comments and tag test cases, against each story ultimately bringing end-to-end traceability.
- Since distributed agile requires more collaboration, JIRA's seamless integration with communication tools like HipChat and Slack allows teams to work collaboratively.
- JIRA supports customization since each team is unique, you can create your own issue types, modify the workflows, add/remove fields.
- Standard issue types created in any project are: a) Bug b) Task c) Sub-Task d) Epic e) Support Ticket f) User story
- User Story workflow can be: a) Backlog b) Ready to Start c) Dev In-Progress d) QA In-Progress e) Ready for Demo All these can be modified based on your requirements.
- If you are looking for devops implementation, JIRA has support for CI & CD.
- It can be integrated with Git and Jenkins very well.
- JIRA supports two kinds of boards, Kanban and Scrum boards. It is very easy to track things using these boards & it also provides ample of charts like reporting options such as burndown charts to help teams plan & replan at every stage in the development life cycle
- Searching issues in JIRA is very simple through JQL (Jira Query Language).
- If we would like to perform a complex search JQL allows to find issues from any timeline.
- The basic version of Jira do not have support for test management, capacity management & release management.
- So users have to buy various plugins to support these basic functionalities which can prove costly based on team size.
- Navigation around the UI can be difficult at times
- Jira is not a simple tool, it requires some training before users can start working on it so some learning curve is involved.
- Jira brings in more team collaboration since teams were geographically distributed by seamless Integration of communication tools like HipChat and Slack which makes it very easy for tracking and responding to notifications.
- Sprints management was relatively simple and straightforward.
- Not cost effective since we needed to buy a lot of plugins for test management, release planning and agile estimation and basic version of JIRA did not support them.
Though with JIRA you need to buy a lot of plugins but it is still cheaper than HP ALM or HPE Octane which is very costly. HP QC is a fully functional software lifecycle tool and probably strongest in its test management capabilities. But in Agile we don't need that extensive test tracking and management so JIRA provides basic tracking and reports that are apt for Agile teams.In HP ALM you can't open another window which is not a problem with JIRA. Also in HP ALM you can't copy and paste some repetitive tasks which can be easily done in JIRA.
Yes
Yes, my organisation can definitely pay based on the issue and its criticality.
I can recall we got stuck with release planning and rather than using manual tools for tasking tracking, we bought the plugin Tempo which was really helpful for effort tacking and drawing trends from previous sprints.
I can recall we got stuck with release planning and rather than using manual tools for tasking tracking, we bought the plugin Tempo which was really helpful for effort tacking and drawing trends from previous sprints.
No
I got stuck with release planning and I got advice on the Tempo plugin from the helpdesk. Also, they helped me with installing ad using that for release planning.
September 20, 2016
JIRA - Love at First Site for Developers, a Slow Courtship for Business
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).
- 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.
- ServiceNow and Workfront
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.
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