Try our new research platform with insights from 80,000+ expert users
Pre-Sales Consultant at a tech services company with 10,001+ employees
Real User
It gives a nice report of my backlog and what my team has currently spent its efforts on
Pros and Cons
  • "Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on."
  • "JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless."

What is our primary use case?

We use it mainly for Scrum management.

How has it helped my organization?

Most of the projects which we have taken in were using a waterfall model, which is very hard to convert into an agile or Scrum model. It helped our customers have visibility into requirements and reporting, since they were mostly using spreadsheets. We could help give them a clear cut view of what was happening on ground with development and the test database.

What is most valuable?

Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on.

What needs improvement?

JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless. 

You can do a lot with the tool but again, but it is not a 100 percent solution for everything. We have a lot of acceptance criteria coming through it, but JIRA doesn't support it. Therefore, we have go to different user stories and break them down. 

Buyer's Guide
Jira
May 2025
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
853,831 professionals have used our research since 2012.

What do I think about the stability of the solution?

Using a cloud instance, it is always stable for us. It is not a problem at all.

What do I think about the scalability of the solution?

We use a cloud instance for most engagement, so scalability has not been an issue.

How are customer service and support?

My company has a 100,000 people, so we always can find someone within our organization who can help fix an issue.

How was the initial setup?

I was not involved in the initial setup.

What's my experience with pricing, setup cost, and licensing?

I understand JIRA is quite expensive.

What other advice do I have?

Most important criteria when selecting a vendor:

  1. Usability: It should be easy to use. People should not have to undergo a lot of training because it should be intuitive.
  2. It should be scalable and a cloud solution. 
  3. It should not be expensive. Cost is a major driver because I work in pre-sales.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
reviewer909060 - PeerSpot reviewer
IT Developer at a financial services firm with 10,001+ employees
Real User
The product is a better way to manage progress and see the status of different tasks. Stability-wise, it is slow and hangs.
Pros and Cons
  • "It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks"
  • "There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level."
  • "Sometimes, it is slow and hangs. We faced some stability issues where JIRA was down for a day. Also, we have lost some of our comments made in the JIRA because of downtime."

What is our primary use case?

We are working in the safe channel process in the IT part of the bank. It is a good experience overall, but the look and feel for the user is not good.

How has it helped my organization?

It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks. Otherwise, it is not possible to work in different geographies.

What is most valuable?

I can drag and drop to the different statuses. I can go into the task and change it, then I can directly drag and drop it from one status to another.

What needs improvement?

There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level. Right now, if I attach something, it will go into a single attachment pool for the task, not at the comment level. I.e., If I want to attach the new version of a document, it creates confusion because I have to remove the existing attachment.

When writing comments, there are not many options for formatting. We were expecting formatting something at the level of Microsoft Outlook or Microsoft Document.

When creating a task, there is no place to add our estimation.

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

Sometimes, it is slow and hangs. We faced some stability issues where JIRA was down for a day. Also, we have lost some of our comments made in the JIRA because of downtime.

What do I think about the scalability of the solution?

I don't have any issues with scalability.

How are customer service and technical support?

We haven't used it.

Which solution did I use previously and why did I switch?

We did not have a previous solution.

What other advice do I have?

I would tell a colleague looking for this type of solution to look at Microsoft TFS and VSTS. 

Most important criteria when selecting vendor:

  • A well-known vendor for the software.
  • A good reputation.
  • Compare what other companies are using.
  • The look and feel of the user interface.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
Buyer's Guide
Jira
May 2025
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
853,831 professionals have used our research since 2012.
R&D manager at a manufacturing company with 10,001+ employees
Real User
We can cope with processes easily without adapting the tool, but adapting the tool to processes
Pros and Cons
  • "We can cope with processes easily without adapting the tool, but adapting the tool to processes."
  • "There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes."

What is our primary use case?

The primary use is task management. It has performed okay. It is easy to configure and maintain. It's quite simple to track tasks, then link with other applications/solutions from Atlassian, like source codes.

How has it helped my organization?

  • Visibility
  • Avoids emails and exchanging information in an informal way. 

I would rather have a tool that we do everything on. Also, we have access to end user policies where we can configure them and give access to the correct person. We have tracking of who works on what and why over the history of a project.

What is most valuable?

Workflows, because we cannot employ a different approach depending on the speed of the project or customer. Whether it's research, engineering, or maintaining the process, we can cope with processes easily without adapting the tool, but adapting the tool to processes.

What needs improvement?

There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes. So, you have to use some add-ons and create a lot effort to obtain information from the tool. Thus, you have to adapt to the lack of search that the tool does not offer.

For how long have I used the solution?

Three to five years.

What do I think about the stability of the solution?

So far, so good.

What do I think about the scalability of the solution?

I don't see any problem with it.

How are customer service and technical support?

In the past, I had training from the distributors and it was okay. 

The tool is very easy to use. What is important is that we don't have to wait so much for contracts or more hours to have support. This is something that we have, and it is good for this solution.

Which solution did I use previously and why did I switch?

Everywhere that I worked, we started by using spreadsheets, then we moved to some free tool, and finally to JIRA.

How was the initial setup?

As far as I know, the initial setup was very simple and straightforward.

What other advice do I have?

Understand your own process: What you are looking for, the size of your company, what your budget is, and the larger plans for the future. There are tools that scale better than others and there are solutions that fit to both small and big teams. There are tools which scale better for larger companies. 

Most important criteria when evaluating a vendor: 

  • We evaluate the company's strategy.
  • If they bought an legacy solution to add to the portfolio or if they are developing from scratch.
  • What are their plans for the future?
  • What type of support do they have?
  • What is their business model? 
  • Do they have domestic experience or not?
  • Are they focusing only on a few customers, and the size of those customers?
Disclosure: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
it_user809520 - PeerSpot reviewer
QA Automation at a tech vendor with 501-1,000 employees
Real User
Allows us to rewrite and change tasks, add columns and change components
Pros and Cons
  • "The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components."
  • "I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice."

What is our primary use case?

We use JIRA for maintaining tasks and bugs. Overall, we love using JIRA because it performs very well with a lot of tasks and a lot of dashboards.

How has it helped my organization?

Having a tool to manage all your tasks and all your bugs is very useful for any company. We use it a lot to keep track, to see how our development is going and how automation is going.

What is most valuable?

We use a lot of dashboards and a lot of queries to search for specific bugs related to specific versions. Also, we can provide it to all of our users throughout the company.

The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components. It gives you a lot of flexibility between the teams.

What needs improvement?

I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.

What do I think about the stability of the solution?

We have had no problems with stability. We're doing maintenance upgrades, but it has working well all the time.

What do I think about the scalability of the solution?

We're not dealing with the scalability because we're not IT, but I don't think there is a problem with scalability.

Which solution did I use previously and why did I switch?

We used Bugzilla but its UI was not as user-friendly. The end-user experience was very basic because it's a free tool. It's important to us that QA be able to track the issues and, of course, for the developers to be able to track all the tasks. So we're looking for the balance between performance of the user interface and the UI for the other workers in the company.

What other advice do I have?

I would rate it at nine out of 10 because there is always room for improvement, but we love this tool and we use it a lot.

I would recommend JIRA. Compare all the tools for bug and task management. After that, you'll see that JIRA is by far the best.

Disclosure: I am a real user, and this review is based on my own experience and opinions.

PeerSpot user
it_user809571 - PeerSpot reviewer
Java Development Team Leader at Honeywell
Real User
Makes the work process transparent, enables communication among various teams
Pros and Cons
  • "JQL, JIRA Query Language enables me to filter all the issues, display the items as I want."
  • "It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable."

    What is our primary use case?

    The primary use case is task management within the team and the company, as well as version management and bug management.

    How has it helped my organization?

    It makes the work process transparent, visible to everyone who needs to know about the current state of the versions, and all that happens. It helps to communicate among different teams, like support, R&D, and QA. Everything is in one place and everything is communicated in the same form.

    What is most valuable?

    JQL, which is JIRA Query Language. I can filter all the issues, display the items as I want.

    It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable.

    What needs improvement?

    I'm using the old version. I haven't upgraded to the new one, so maybe a feature I would be looking for is already there. I don't know. Something I had been looking for was pasting screenshots into issue details, but this was already implemented in the new version. 

    Better user management features could help.

    What do I think about the stability of the solution?

    I have no problem with stability.

    What do I think about the scalability of the solution?

    I don't have problems with the scalability. I know companies that are much larger than just projects or teams, that are much larger than my current team, and they work with JIRA and it works well.

    How is customer service and technical support?

    I used the support from JIRA several times and it was good. I had questions about licensing, I had questions about upgrading from an old version to a newer version.

    What other advice do I have?

    When I am evaluating a product or vendor, I have some intuition about it. I see how the thing is built and works, and I go by my own impression. For me, that is important. And, of course, price and maturity of the product, along with flexibility, are important criteria.

    I would rate this solution a 10 out of 10. It's an excellent product. It has already improved. It has good support. From the beginning, it was very smart and customizable and built well, works well. There are almost no bugs that I have discovered. It's a good product.

    I just saw an advertisement on the street for a product called Monday.com. I read a few lines, a few words about it. I hadn't heard of it before that, but I understand it does something similar to JIRA. Obviously, I can recommend using JIRA but if you are searching for something else, the first impression I got from reading the home page of Monday.com was good, so maybe it's worth evaluating.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.

    PeerSpot user
    PeerSpot user
    Manager, Live Production at a computer software company with 1,001-5,000 employees
    Real User
    The mobile app functionality needs improvement. It can be customized for different teams.
    Pros and Cons
    • "I found it super useful, as it is customizable for different teams and users."
    • "The following definitely need improvement: UI, speed, and mobile app functionality."

    What is most valuable?

    Overall, everything with it is great. I found it super useful, as it is customizable for different teams and users.

    What needs improvement?

    The following definitely need improvement:

    • UI 
    • Speed 
    • Mobile app functionality.

    What do I think about the stability of the solution?

    It is consistently slow.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.

    PeerSpot user
    PeerSpot user
    Business Analyst, Scrum Master & Agile Coach at Atos
    Consultant
    Relatively easy for everyone to pickup and use
    Pros and Cons
    • "It improved communication, as it was a popular tool, and most people enjoyed using it."
    • "Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to."
    • "Out-of-the-box reporting is limited. It would be helpful if more customisation was possible."

    What is our primary use case?

    • Running agile deliveries with dispersed teams. 
    • The projects were typical agile, changing requirements frequently.
    • JIRA facilitated story management perfectly.

    How has it helped my organization?

    • Overall, it has good viability. 
    • Relatively easy for everyone to pickup and use. 
    • It improved communication, as it was a popular tool, and most people enjoyed using it.

    What is most valuable?

    Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to.

    What needs improvement?

    • Report customisation could be improved. 
    • Out-of-the-box reporting is limited. It would be helpful if more customisation was possible.

    For how long have I used the solution?

    One to three years.
    Disclosure: I am a real user, and this review is based on my own experience and opinions.

    PeerSpot user
    it_user855996 - PeerSpot reviewer
    Integration Engineer at a tech services company with 10,001+ employees
    Real User
    ​It is very capable, but also very complicated
    Pros and Cons
    • "It is very flexible, so we can do pretty much what we want with it."
    • "It handles all of the issues that we need it to do."
    • "​I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.​"
    • "I do know the initial setup was pretty complicated. The user interface could be better organized and easier. ​"

    What is our primary use case?

    We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

    How has it helped my organization?

    It handles all of the issues that we need it to do.

    What is most valuable?

    It is very flexible, so we can do pretty much what we want with it. 

    What needs improvement?

    I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.

    What do I think about the stability of the solution?

    It is stable.

    What do I think about the scalability of the solution?

    It scales up well.

    How are customer service and technical support?

    We have a team who administrates technical support. They handle this interaction with JIRA. Sometimes it takes a while to get a solution, but they solve everything. 

    Which solution did I use previously and why did I switch?

    Before, we used a homegrown solution. 

    Almost everybody uses JIRA nowadays because it is the most cost-effective solution.

    How was the initial setup?

    I was not involved in the initial setup. 

    I do know the initial setup was pretty complicated. The user interface could be better organized and easier. 

    What's my experience with pricing, setup cost, and licensing?

    It does not cost that much.

    Which other solutions did I evaluate?

    We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

    What other advice do I have?

    It is very capable, but also very complicated.

    Most important criteria when selecting a vendor: reliability.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.

    PeerSpot user
    Buyer's Guide
    Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.
    Updated: May 2025
    Buyer's Guide
    Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.