JIRA: Product is well liked but we have had performance issues. Premier Support: Knowledge is very good and they are willing to bring in other people when they need to. The Premier Support team was very thorough and very responsive.
Systems Architect at a tech company with 10,001+ employees
Allowed us to not waste time with dead ends, better focus, and get to root cause much faster.
What is most valuable?
How has it helped my organization?
I think that if you look at how we troubleshoot, Premier Support has allowed us to not waste our time with dead ends, to have better focus, and get to root case much faster. Even though we still have monitoring in place, for root cause analysis we rely heavily on Premier Support and don’t waste as much time.
What needs improvement?
For our Premier Support, We would like to have on the call interaction all the time. The session we’ve had recently has been valuable, but we would like to see more live sessions/interactions.
For how long have I used the solution?
Purchased Sept. 27th 2014.
Buyer's Guide
Jira
December 2024
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What was my experience with deployment of the solution?
Our Premier Support engineer was extremely helpful with deployment. I was pleasantly surprised, the engineer gave us guidance, looked for any potential issues, and was above and beyond in terms of service. They did a really fantastic job.
What do I think about the stability of the solution?
From the beginning that has been the main thing we have been working on and thru Premier Support, they have done a good job working on our side, and escalating to a larger team when needed.
How are customer service and support?
Customer Service:
The Premier Support team was very thorough and very responsive.
Technical Support:The Premier Support team was very thorough and very responsive.
Which solution did I use previously and why did I switch?
We previously used the standard Atlassian support and then jumped from standard to premier. In terms of tracking, we had other defect tracking, but now JIRA has been a replacement – it is the tool of the future.
How was the initial setup?
The initial setup was straightforward.
Which other solutions did I evaluate?
Yes, we have other vendors and tools – evaluation is ongoing.
What other advice do I have?
I would tell people to understand your growth and usage up front – really comes down to understanding that and keeping it under control. We grew too fast and weren’t prepared for the issues that came with that; you want to make sure you have a good performance testing environment in place, datacenter etc. so you’re not scrambling afterwards.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Principal performance architect at a comms service provider with 501-1,000 employees
User-friendly and helps monitor stories, scrum updates, and Definition of Doneness (DoD)
Pros and Cons
- "The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks."
- "The solution's stability could be improved, and it could be made more robust."
What is our primary use case?
I have worked with Jira for agile scrum projects. Jira is a good tool that helps you track and monitor all your stories, scrum updates, and Definition of Doneness (DoD). We can track everything we need to track and pull the reports from the Jira tool. Based on the team's activity, we can monitor, track, and update the tasks we have assigned through Jira. We also use Jira for sprint planning.
What is most valuable?
The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks. You can export and play around with the reports. In the defect tracking tool, you can pull the data and generate reports with a nice graph. It's very user-friendly. The solution's user interface is intuitive and easy to use.
What needs improvement?
Sometimes, Jira becomes slow when more people use it. Then, we have to close it and log in again. The solution's stability could be improved, and it could be made more robust.
What do I think about the stability of the solution?
I rate the solution’s stability a seven out of ten.
What do I think about the scalability of the solution?
Around 2,000 users use Jira in our organization.
I rate the solution an eight out of ten for scalability.
How was the initial setup?
The initial setup of the solution is very simple. You can install Jira as a standalone solution. Deploying the solution on the cloud is very, very easy, and then you can access it from anywhere on the cloud.
What other advice do I have?
I have used Micro Focus Quality Center, which is purely a defect management tool. We can also use Jira as a defect management tool. When you compare both tools, Jira is now the best tool for defect management and running scrum projects. You can even expose the Jira APIs to do automation.
If you find a defect, you can automate the process of logging in to Jira and erasing the incident. When you find a defect while running JMeter scripts, you can take the APIs and automate it to save time. The automation process can be done through Jira because it exposes its APIs to third parties to integrate with other tools.
You can expose Jira APIs and integrate the solution with other tools. You can have your own dashboard using the APIs. I would recommend the solution to other users.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Apr 11, 2024
Flag as inappropriateBuyer's Guide
Jira
December 2024
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
Software Engineer at a tech vendor with 10,001+ employees
Confusing terminology, difficult to use, but simple user interface
Pros and Cons
- "The design of the interface is clean and not too busy visually."
- "I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues, epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand."
What is most valuable?
The design of the interface is clean and not too busy visually.
What needs improvement?
I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues, epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand.
When you want to create something in Jira, whether it's a story or an epic on a task, you have to create a thing called an issue, and inside the issue, you have to put what type of issue it is. Either it's an epic or a story. The fact that it's called an "issue" was a little confusing for me because I didn't know where to search when I wanted to look for tasks and stories. I didn't know that I needed to search for issues and not only tasks or topics.
For how long have I used the solution?
I have been using Jira for approximately one month.
What do I think about the stability of the solution?
Jira has been a stable solution.
What do I think about the scalability of the solution?
I have found Jira to be scalable.
We have 20 people in my company using Jira.
How was the initial setup?
The setup of Jira was simple.
Which other solutions did I evaluate?
I did not compare Jira to other solutions.
What other advice do I have?
I have not had a lot of time to explore the solution. My rating might be higher if I had used it more.
I rate Jira a three out of five.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Head of QA Testing Services at a tech services company with 10,001+ employees
Reliable, scalable, but installation could improve
Pros and Cons
- "I have found Jira to be stable."
- "The integration could be better in Jira."
What is our primary use case?
We are using Jira for our test management. We're using it to record our inspecting results and to regulate the evidence in the report.
What needs improvement?
The integration could be better in Jira.
For how long have I used the solution?
I have been using Jira for approximately 15 years.
What do I think about the stability of the solution?
I have found Jira to be stable.
What do I think about the scalability of the solution?
Jira has been scalable.
What's my experience with pricing, setup cost, and licensing?
There is an annual subscription to use Jira.
What other advice do I have?
I would recommend the solution to others. I have been happy with Jira.
I rate Jira a seven out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Engineer at a financial services firm with 10,001+ employees
Provides high visibility into the development pipeline
Pros and Cons
- "When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
- "I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
What is our primary use case?
Currently, we're using it as a tracking tool. It helps our development department operate more efficiently while enabling the business side of the company to understand and track things better. For example, if we get a requirement from the business side, they don't tell us the status of the current cover every time. So basically what we do, if we complete development or make it to the development phase, then we can change the status in Jira. If the other departments want to see the progress, they can go to the Jira dashboard. So this reduces the amount of necessary communication between the business side and developers. Developers can mainly focus on the development instead of having to answer questions from other departments.
What is most valuable?
When we get a sign-off for a management request, we must catch it in our email inbox. Now we can get the sign-off through Jira, and I've automated this. For example, we can get the Jenkins pipeline results for every build we create and have that result plugged into Jira. So when we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool. If you open Jira, you get the development tab there, so you can find out everything a company made under this Jira or what brand is created under this Jira. As a developer, I find this feature valuable.
What needs improvement?
Jira could be simplified and integrated more with standard corporate communications tools. Say, for example, we have one indication of Jira in Confluence. So if we type a Jira ID into Confluence, it gives us all the information about the Jira profile. I would like to see this feature integrated with email platforms so we can just put our Jira ID or Jira link into an email and get all the details automatically. This kind of integration and automation would be helpful.
I'd like to see better note-taking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile. It's not something for the business side, but developers can track what work is finished and what still needs to be done. Jira could integrate better with Jenkins, which isn't fully supported on the Jira dashboard yet. I think it would be good to monitor the build's progress directly. That way, we don't have to attach it. We can do it from the background. Some workflow customization would also be good.
For how long have I used the solution?
In the initial phase, I was using Jira for development and testing purposes. A story was assigned to me, and I just changed the standards and everything. But in the past six months, I have worked with configurations, adding different workflows, and all the other features.
What do I think about the stability of the solution?
Jira is pretty stable most of the time. However, we have an intranet on our side, and sometimes there are too many users. My company currently has four different departments at the top level. Each of the four departments has fewer than nine Jira users. My current department has approximately seven or eight users. So there are times when Jira goes down, and we find it difficult to log in. But we are trying to increase the capability of servers. Other than that, it's working fine.
What do I think about the scalability of the solution?
We have migrated to GCP, and we're using the internal cloud servers, so we can easily integrate Jira into a server if we want. Scalability is a matter of cost. We just need to present our management with a valid reason for increasing capacity, and if they approve, it's an easy process for us.
How are customer service and support?
We had to call Jira support for help with integration. For example, when I was trying to integrate Jira with my GitHub bot, I had to provide a specific kind of access and then run some scripts to find out if I had enough available space. After that, it's a smooth process.
How was the initial setup?
The Jira setup is a bit complicated because we're deploying it in our internal servers. So we have to manage a lot of things ourselves. For example, when the new version of Jira comes in, we have to patch our servers and update our certificates. And then, for deployment, we have pipelines that we need to trigger. That's not too hard, but the patching and upgrading can be complex.
If it's a smooth deployment, it just takes 30 minutes because we only have to replicate it on a different server. So currently, we have more than 20 servers. So every time we deploy, we create a replica on every server, which takes time because we have to verify that it's working. In total, it's about two hours of downtime in Jira, so we do this at night.
Currently, more than 10 people are involved with maintenance. For my team, I do the deployment and configurations. But if there is some fundamental change or a serious bug, a separate team handles this.
What's my experience with pricing, setup cost, and licensing?
I don't deal with the money side of things. I just specify the requirements and the company handles everything. We are using it for many tasks so it seems like the price is reasonable.
What other advice do I have?
I rate JIRA eight out of 10. I think it's a great tool. I have been working with this tool for the past two years and I use it every day.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
CEO at a transportation company with 1-10 employees
An issue tracking solution with a nice GUI
Pros and Cons
- "In general, the GUI is nice."
- "The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly."
What is our primary use case?
I'm working on creating test cases and one test. I also have an overview of the Sprint.
What is most valuable?
In general, the GUI is nice.
What needs improvement?
The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly.
For how long have I used the solution?
I have been working with Jira for about eight months.
What do I think about the stability of the solution?
Jira seems like a stable product, but sometimes I'm losing data.
What do I think about the scalability of the solution?
As a totally different team does the entire setup, I don't know if it's scalable. But we have about 150 users.
Which other solutions did I evaluate?
To be quite honest, at the end of the day, a tool is just a tool. For me personally, it's hard to say this tool is much better than the other. From just what I know so far, Micro Focus Octane looks a bit more modern. But I don't know which Jira version we're using at the moment. Octane looks a bit more integrated, it looks a bit newer, but would I buy a tool because of that? Certainly not.
What other advice do I have?
I would recommend Jira for Sprint management. But when it comes to documentation of manual tests, I would say, "Okay, you can buy it if you want to have one package, but you can also have a look at something different."
On a scale from one to ten, I would give Jira a solid eight.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
User-friendly and provides very good visibility and traceability, but should have role-based access and more reports
Pros and Cons
- "It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust. It is working well, and there are a lot of add-ons or plug-ins out there that you can use."
- "It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
What is our primary use case?
It is used by the agile teams for product development and feature management.
What is most valuable?
It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust.
It is working well, and there are a lot of add-ons or plug-ins out there that you can use.
What needs improvement?
It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira.
I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports.
For how long have I used the solution?
I have been using this solution for five years.
What do I think about the stability of the solution?
It is stable. I don't see any instability in Jira.
What do I think about the scalability of the solution?
It is easily scalable. We have around 1,500 users.
How are customer service and technical support?
I have not directly interacted with Jira's technical support. We have an internal Jira service desk for any issues.
Which solution did I use previously and why did I switch?
I have used HP ALM, version 11, and it was not so robust. I found Jira to be more robust. In HP ALM, you can define the requirements and test cases and map them, but you cannot see the in-depth requirements, whereas Jira provides more visibility, and you can see each and every part of a process very clearly. It is more open and user-friendly.
Traceability is very important for the SDLC process, testing lifecycle, and audits, which is one of the key features that Jira provides. It provides detailed traceability so that you can easily know about the sprints and change requests. With HP ALM, you can define requirements only in one or two lines. It is more of a testing tool. It is not a development lifecycle tool.
How was the initial setup?
The initial setup for Jira was done by a third-party vendor, so we did not face any issues. The migration from an older application to Jira was not so easy, and it required a lot of effort.
What about the implementation team?
It was implemented by a third-party vendor. It requires maintenance, but it is not so difficult to maintain. For maintenance and administration, we have an internal Jira service desk.
You need to do upgrades because you tend to have requirements from different stakeholders. You also have different add-ons and plugins, and Jira also keeps on releasing new versions that might be useful.
What other advice do I have?
I would recommend this solution. I would rate Jira a seven out of ten because there are some areas to be improved in Jira.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Solutions Architect with 11-50 employees
A very capable product with many useful features, impressive scalability, and good stability
Pros and Cons
- "Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work."
- "Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it."
What is our primary use case?
We are mainly using it for project management and issue tracking. It is used by development, QA, and IT operations. It really goes through the whole gamut of project management.
We are not using its latest version. We are usually a little bit behind on versions.
What is most valuable?
Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work.
What needs improvement?
Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it.
For how long have I used the solution?
I have been using this solution for probably six years.
What do I think about the stability of the solution?
Its stability has been very good. Every once in a while, we have a problem, and the service stops working. I don't think we have a very robust installation of it, but if there is an issue, it is back online very quickly.
Most of the issues are probably related to the server needing patching or something else. It may not be running on the appropriate size hardware. I know it is not a well-funded product at our office.
What do I think about the scalability of the solution?
It is impressive. We have all our projects on it, and we haven't really had reports of any issues. We haven't yet stretched it to its limitations, but it has managed to meet our requirements, even in this minimal deployment. I am pretty impressed.
How are customer service and technical support?
I didn't directly contact them, but I am sure at some point we have. We usually have a contact person, and we pay for the full support.
Which solution did I use previously and why did I switch?
We are adopting multiple products, such as ServiceNow, but they do different things and are for different purposes. There is a talk about replacing Jira with ServiceNow, and we're not too happy with it because we all liked Jira, but sometimes this kind of stuff happens. ServiceNow does have crossover features, but it gets into problems for us when changing from one system to another.
How was the initial setup?
I didn't set it up, but I haven't heard of any issues with the implementation of it. It seems to be very straightforward.
What other advice do I have?
I would recommend this product. Overall, it is a good product. It supports scrum and agile developments. It has a lot of benefits that can be applied very quickly in organizations.
I would advise others to do a test installation and make sure that it fits their needs. Experiment with the multitudes of features that it has. I know there are lots of modules. There are probably many features that we are not using.
I would give it very high marks. I would rate Jira a nine out of ten. There is always something you could improve on it.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Product Categories
Application Lifecycle Management (ALM) Suites Application Requirements Management Project Management SoftwarePopular Comparisons
Microsoft Azure DevOps
TFS
OpenText ALM / Quality Center
OpenText ALM Octane
Rally Software
Polarion ALM
Jira Align
Codebeamer
Jama Connect
PTC Integrity
Helix ALM
Digital.ai Agility
IBM Engineering Rhapsody
Planview AgilePlace
Atlassian ALM
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Has anyone tried integrating HP ALM and JIRA ?
- Can JIRA provide integration to SAP automation?
- What Is The Biggest Difference Between JIRA And Microsoft Azure DevOps?
- What Is The Biggest Difference Between AgileCraft And JIRA?
- What is the biggest difference between JIRA and Micro Focus ALM?
- Which is better - Jira or Microsoft Azure DevOps?
- Is Jira better or would you go with Micro Focus ALM Octane?
- Is Jira a suitable solution for both agile and waterfall projects?
- Which tool is integrated better with Jira - Micro Focus ALM Quality Center or TestRail by Gurock?
- What are the equivalent Microsoft tools to Atlassian Confluence and Jira?