Jira Overview

Jira is the #1 ranked solution in our list of top Application Lifecycle Management Suites. It is most often compared to Microsoft Azure DevOps: Jira vs Microsoft Azure DevOps

What is Jira?

JIRA has multiple deployment options to provide the flexibility your organization needs.

Cloud is a fully hosted service for customers who want to iterate quickly and have us take care of managing the infrastructure.

For customers who need to run our applications behind their firewall, we have Server and Data Center options. Server delivers greater capacity for a larger user base and gives you more control, allowing you to remain compliant with your enterprise IT, security, IP and privacy policies. For our largest customers, Data Center provides all the capability of our Server option, along with high availability, instant scalability and performance at scale.

Atlassian also offers premium support and strategic services for enterprise customers. Technical Account Managers are cross-functional technical advisors providing proactive planning and strategic guidance across your organization. Premier Support goes above and beyond our standard offerings to give you account-wide support from a team of senior support engineers.

Jira is also known as Jira Software.

Jira Buyer's Guide

Download the Jira Buyer's Guide including reviews and more. Updated: July 2021

Jira Customers

Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.

Jira Video

Pricing Advice

What users are saying about Jira pricing:
  • "I am not sure about the pricing, but I know its licensing is on a yearly basis."
  • "For very small companies, if you have less than 10 individuals, it is $10 a year for each of the products. When we were a part of the enterprise and had more than 10 people using it, or before they came up with this solution for small companies, it was $2,500 a year for the license for Jira and Confluence, and I believe something like $600 a year to perpetuate the license. I can't remember if it was $600 or $2,500 annually. It was for up to 25 people at the time, and this was in the early 2000s and mid 2000s."
  • "Jira and its solution off the shelf are cheap. It is cheap for startups."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
RobertCampbell
Product Manager at a insurance company with 10,001+ employees
Real User
Top 20
Great for collaboration, very stable, and extracting data is straightforward

What is our primary use case?

We are using the product for general task management, largely. From a software development community perspective, obviously, we use the task management piece - the foundation to what leads into the development and the CI/CD pipelines and et cetera. Outside of that, it varies widely. At its very core, it's task management, however, then it's used by various functional areas within the company. For example, we have contracting and procurement that utilize it. And we have marketing that uses it and security, IT security, audit, compliance. Various functional areas across the company use Jira. We… more »

Pros and Cons

  • "You no longer need to email people. You can mention them right in Jira and have conversations there."
  • "In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."

What other advice do I have?

We're just customers and end-users. I upgraded the application back in December, so we're on 8.13 right now. While we're currently on-premises, one of the things that were on my to-do this year was to consider moving to the cloud, which is something that we are very interested in doing. Currently, we're using the Jira Data Center. Our company has barely scratched the surface of the power of Jira in my personal opinion as they've just largely tried to do a bunch of customization. There was no governance set when I first joined the organization. People were just allowed to create whatever they…
VN
Senior PM / Scrum Master at a financial services firm with 1,001-5,000 employees
Real User
Top 5
Stable and easy to learn with good customizations, useful burndown charts, and support for a query language

What is our primary use case?

I work with a credit rating company in the US. As a scrum master and project manager, I have to make sure that all the impediments are removed for the team. I work with product owners to make sure that all initiatives requested by our stakeholders, who are mainly compliance and regulations people, are moving in a timely manner. I use Jira to make sure that we are capturing all the work that is requested, and it is progressing in a timely manner. I am in charge of a squad called Core Operations Reporting. A squad is usually focused on one or two initiatives. The goal of our squad is to automate… more »

Pros and Cons

  • "It was very easy to learn Jira. As a scrum master, I run daily stand-ups, and they are run directly from Jira. The feature that I really love in Jira is called Issue Navigator. It allows me to customize how I want to show the user stories within Jira to my squad."
  • "I can use Jira Query Language (JQL) to write queries to see the stories that are there for the current sprint. I can also sort them by assignment. I also use Jira is for burndown charts, which give an indication of how efficiently the squad is performing. I also use the Active Sprints function and a feature called Planning Poker."
  • "One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. When Epic Link's background color is a dark color, it effectively becomes unreadable. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view."
  • "There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
  • "I also wish Jira had an indicator to tell you that you are approaching the limit for the story points that can be delivered during a sprint. I don't think there is an indicator like that, but such an indicator will be very helpful because then I will be easily able to see that we are approaching the limit."

What other advice do I have?

The main advice would be to just use it as much as possible and try to learn the basics of JQL, which is Jira's proprietary language that allows you to tell Jira exactly what you want to see. It is pretty self-explanatory and not hard to use. There are so many different fields in Jira such as issue type, key, sprint, summary, Epic Link, reporter, assigning, status, story points, and components. You can add the required columns to the Issue Navigator view, and it will spit back exactly what you wanted to see. You should also learn what kind of value it can add to the organization before just…
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
521,690 professionals have used our research since 2012.
Gesner Herard
Senior Principal Engineer at a consultancy with 1-10 employees
Real User
Top 20
A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy

What is our primary use case?

We have different software projects. I primarily use Jira to define and plan projects for agile-based project management. We use different aspects. We have scrum-based management for some projects and different systems for others.

Pros and Cons

  • "The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
  • "From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement."

What other advice do I have?

One piece of advice, which they also give in their documentation, is to use your own database management system. They give you something that you can use. It is called HSQL or something like that, but you can use what your company can afford, such as MySQL or SQL Server, and manage that yourself. It will help you to do better data management and backup management. I would use the built-in backup management system as a backup, although I haven't had any problems at all in years. Just for a warm fuzzy, it is always good to have a backup system. I would recommend looking into primary tools…
DavidMason
Consultant at a pharma/biotech company with 10,001+ employees
Consultant
Top 20
An easy-to-understand defect tracking tool with good capabilities and integrations

What is our primary use case?

I'm overseeing the developments done in Jira.

Pros and Cons

  • "It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want."
  • "It also works well with all the integrated tools that you buy."
  • "If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool."
  • "One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."

What other advice do I have?

It depends on what you want to use Jira for, and what's the problem you're trying to solve. If you're going to do defect tracking and management of an artifact and you have got requirements, code, and tests, and they all got to summarize, you have to then go ahead and take Jira. You can then buy Crucible for the peer reviews and Xray for the test management and get them to work seamlessly with each other. I would rate Jira an eight out of ten. It is fairly cheap. For a nine or ten, it would be like DOORS and Jazz platform, but the problem with that is that it would become really expensive.
AO
Head of Software Solutions at a tech services company with 11-50 employees
Real User
Top 20
Flexible and very easy to set up but can get quite complex

What is our primary use case?

We have a service desk for customers. We have the whole flow from customer feedback throughout, committing with a relation in the code in Bitbucket. We have the tracking and tracing, including all tracking of the issues all the way from the customer throughout the JIRA prioritization in backlogs and sprint planning and connecting those through the actual code commit in BItBucket. It's all done through JIRA to the service desk issue and back again to the customer. The entire ecosystem is quite connected.

Pros and Cons

  • "It's really smart how they connected these third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
  • "Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed."

What other advice do I have?

I would guess we are using the latest version of the solution as we're using the cloud solution. I'm guessing that it's continuously updated automatically. I'd advise others to consider the solution. However, It depends on what they're trying to achieve. There are a lot of easier project management tools like Monday.com, for instance. It's a lot easier to get up and running. If your vision is to become a larger software development company, monday.com might be something that is usable for project managers. However, it wouldn't be a good tool, at least how I've seen it, to connect everything…
PO
Technical Lead at a mining and metals company with 51-200 employees
Real User
Top 5Leaderboard
An all-encompassing, project management solution

What is our primary use case?

Virtually every day we have our daily scrum. Our team gathers around the board, which has all the columns showing where the tasks are standing: requested, planning, ready-coding, review, etc. Together, we view one task after the other and update the statuses. It's really a focal point of the team to know where the work stands, and what's the progress of the work since the last time we checked. Within my company, there are roughly 25 employees using this solution. We have a scrum master, who's the most knowledgeable person on the tool. usually, they're the ones organizing the tasks, creating… more »

Pros and Cons

  • "With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board."
  • "There needs to be easier integration with third-parties — personally, this is the biggest issue for me."

What other advice do I have?

Have a training session before you begin using it. That tool is good for teamwork, but it doesn't replace a face-to-face discussion. Among yourselves and your teams, establish some conventions as to how you will describe your tasks — what criteria will be acceptable? Include a section for requirements, have a section dedicated to discovering your setup because the tool has its limits. It helps you organize your work, but it doesn't replace the self-discipline of the developers to stick to some team conventions — that's also really helpful to get the full benefits of that tool. One of the main…
Meryeme Bensouda
Global Client Support Operations Manager at kyriba
Real User
Top 20
Good UI, easy to trace tickets, and very stable

What is our primary use case?

We use it to trace our business needs development. We have some nice dashboards out there where we can track needs for clients or track internal projects.

Pros and Cons

  • "This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page."
  • "Jira has recently updated their UI, but more can be done to make it even better."

What other advice do I have?

I'd advise other companies to go for it and try using it. Jira is one of the biggest players in the market. It's a scalable solution and very user-friendly. The onboarding is quite simple. I have never been trained and I've been using it for the four past years. Whenever there is a new release on Jira, we get a guide, which is helpful, and instructions as we use the latest version that comes in the form of pop-ups on your screen. If you want, you can just disregard it, but once you discover them, you can just hover over with your mouse and you can see the new features. If an organization is…
MallikKesavaraju
Scaled Agile Consultant at Anthem Blue Cross Blue Shield
Consultant
Top 10
Great story maps, an excellent overview of team performance, and very scalable

What is our primary use case?

I have been the product manager for several years. I use it day in and day out to manage my team. I manage two teams at the moment and they are pretty large teams. Each has a minimum of about 12 people. We use not just agile, we use a scale model framework. All the work is managed through two pieces of software we use. One is called Jira Align. For the portfolio level software, what Jira bought recently, the previous name for the software was AgileCraft. All of the portfolios and features come loaded in Jira Align. From there, they will be composed into stories in Jira. That process is done… more »

Pros and Cons

  • "The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view."
  • "Whenever you edit a story, whatever you have changed takes a bit of time to save."

What other advice do I have?

We are using the latest version of the solution. It's a great piece of software. If you really want to do agile software project management Jira is definitely should be a top choice for you. I'd rate the solution eight out of ten.
See 72 more Jira Reviews