Skip to main content
TrustRadius
Atlassian Jira

Atlassian Jira

Overview

What is Atlassian Jira?

Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.

Read more

Learn from top reviewers

Return to navigation

Pricing

View all 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
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 Atlassian Jira?

Atlassian Jira 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

Atlassian Jira 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

Atlassian Jira Competitors

Atlassian Jira Technical Details

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

Frequently Asked Questions

Atlassian Jira is a project management tool, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.

Atlassian Jira starts at $81.85.

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

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

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

Comparisons

View all alternatives
Return to navigation

Reviews From Top Reviewers

(1-5 of 123)

Manage your projects with a simple and easy to use interface

Rating: 9 out of 10
August 17, 2019
HM
Vetted Review
Verified User
Atlassian Jira
2 years of experience
It is being used throughout our organization. We use it to plan, monitor and develop your projects quickly and easily. With Jira, plan your daily work by creating user stories, incidents or assigning tasks and subtasks to your team members. Integration with the main development environments such as Eclipse, Visual Studio, Netbeans, make it an effective and productive alternative.
  • It is very simple, basic and simple to use.
  • It allows precise customizable estimates according to the needs of the project.
  • You can have administrative control of the company's activities (projects, processes, procedures).
  • It is compatible in virtually all databases.
  • It offers Web access with support for the main browsers in the market, email notifications, as well as many applications that provide additional resources to Jira.
Cons
  • Although Jira is an excellent tool for project management, the cost can be somewhat expensive.
  • Its initial configuration proved to be complicated.
  • It can be difficult for beginners, because it is difficult to understand its characteristics.
Jira is a considerably flexible application that allows you to start coordinating and controlling semi-structured processes. It allows you to define different types of incidents or tasks. These can be linked to the same workflow or to different workflows. It allows each user to define their own filters and dashboards, share them or use those defined by other users.

Best Defect Tracking Tool

Rating: 8 out of 10
January 25, 2015
RM
Vetted Review
Verified User
Atlassian Jira
5 years of experience
Atlassian JIRA is used across all teams(Development/Business Users) across organization. It is used for Tracking defects, creating projects and listing CR's, Tasks. It provides a variety of features like creating projects, dashboards, interface with fisheye, gitcodebase etc. So every small detail and its history can be tracked within JIRA. The new JIRA version has a beautiful user interface and easy to use. My team also uses it to link JIRA with HP Quality Center which is a great addition.
  • Atlassian JIRA is used to track defects/CR's etc. Details about the defect raised by a QA, then its review by business users to give a go ahead to fix the bug, Developer to analysis and fixing the bug with comments, deploying to QA for testing, Tester testing the defect and then into UAT for business user testing for its deployment to Production
  • Integration with Fisheye, Stash, GIT, HP Quality Center etc
  • JIRA's project Dashboard for tracking all the stories/defects.
Cons
  • The new version of JIRA is a bit slow and not responsive.
  • A lot of functionality added has lead to slowness in the tool
  • A click here and there leads to opening a small window for adding comments which can be irritating sometimes.
JIRA is a very good tool for defect tracking purpose. Its even better than HP Quality Center. It's a better tool when you have to log every small detail for tracking. Creating dashboards are pretty easy to do. You can track defects from other teams as well. Integration with other tools like SVN, Stash, Fisheye etc. Very good interface. Attachment options. Simple drag and drop facilities. Creating different user avatars. Analysis of project tasks. Creating reports. Assigning links of other defects which also shows the status of the linked defect etc. Overall a very good tool.

Very few issues with managing issues

Rating: 8 out of 10
March 20, 2017
Vetted Review
Verified User
Atlassian Jira
2 years of experience
JIRA is used by R&D in order to work on adding features and improvements, as well as identifying and repairing bugs. JIRA is also used by engineering for working on server and data center issues. Lastly, JIRA is used by application support at a tier 2 and tier 3 level for troubleshooting single user issues.
  • Creating dashboards for issue tracking and management.
  • Highly customizable and many plugins are available.
  • Logging, tracking and updating issues via email.
Cons
  • Useful for project management but not flexible enough to effectively use for other purposes.
  • The search function is poor.
  • Interface is not terribly user-friendly.
JIRA is very well suited for project management and issue tracking. JIRA is extremely customizable and effectively used to track specific issues easily or display a larger overview of all projects.
JIRA is not an effective change or problem management tool. It also has a complicated user interface and there is a bit of a learning curve, but that is fairly easily overcome with continued regular use.

JIRA - Love at First Site for Developers, a Slow Courtship for Business

Rating: 8 out of 10
September 20, 2016
Vetted Review
Verified User
Atlassian Jira
2 years of experience
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.
Cons
  • 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.

JIRA Software Review

Rating: 10 out of 10
March 28, 2020
RC
Vetted Review
Verified User
Atlassian Jira
4 years of experience
We use it to enter all requests; vet their research thru discovery; assign resources, points, sprint, deadlines, watchers, labels, components, etc.; publicize progress to all parties; configure dashboards to enable managers to make decisions; and house all our historical works for future reference. It is in the cloud thus accessible from anywhere. Our centralized directory runs its single-sign on thus no need to make accounts. User data from that directory is shown in JIRA thus speeding up contacting. It solves lack of mutual visibility, accountability, standardizing tags/labels, mass assigning tasks, organizing a formerly email-based workflow, and forces discipline.
  • Labels enable all the benefits of tagging-based organizing
  • Webhook with Git means we can see all commits per task(s) cited in the commit message
  • Easy single-sign on integration removes need to create new accounts
  • Frontend is super fast which promotes users taking even complex tagging actions
  • No problems integrating with Confluence (Wiki-like) and BitBucket (Git-like) for productive quick starts.
Cons
  • Mass-editing and scripting to, say, mass-rename a set of labels to a new one or many
  • Command line interface would be nice, for power users
  • Version number is difficult to find leading to difficulty judging what version we run thus which features we are truly missing
  • Eorkflow edits aren't protected from errors/inconsistencies like mapping a label to null
  • Workflows can be loop-to-self, be massively inefficient, should be a workflow "linter"
We have a project with 30 users finding multiple issues daily due to the project's complexity in all senses: business-wise, politically, technically, developer resource constraints, time constraints, and limited intake managers. That said, we must be very efficient and judicious about how we file all the reported errors, new features, critical bugs, re-categorizing in between, etc. JIRA's great interface allows us to search and tag and make fast large-scale edits to this torrent of tasks to bring it into order. The public visibility and linking tasks also helps organizing such a large volume of tickets with so few people. Without JIRA, either people wouldn't be able to submit requests at all to a sane system or the interface would be so dissuading as to cause them to not speak up. JIRA is the tool to tame a beyond-human scale of requests.
Return to navigation