Try our new research platform with insights from 80,000+ expert users
reviewer1675329 - PeerSpot reviewer
IT Manager at a government with 10,001+ employees
Real User
Easy to use and easy to onboard, but needs better documentation and better integration with other tools
Pros and Cons
  • "It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
  • "If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side."

What is our primary use case?

We had a regulatory requirement through our legislature to collect motor or voter information for residents of California. So, if you basically wanted to sign up to vote, you could do so at a department of motor vehicles. The Jira instance was used for what we call the new motor voter, which is the online premise to register to vote when you conducted a DMV transaction, such as vehicle registration, driver's license, renewal, etc.

We had its latest version. It is online. In the cloud, we set up an account for the department, and then add users as needed. It is a government cloud.

How has it helped my organization?

It documented our business requirements.

What is most valuable?

It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing.

What needs improvement?

If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side.

Another enhancement could be in the area of interfacing with other products or connectivity. It could have better integration with other tools.

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

For how long have I used the solution?

I have been using it since 2017. It has been about five years.

What do I think about the stability of the solution?

Its stability is good. There are no issues with the performance.

What do I think about the scalability of the solution?

Its scalability is fine. At the peak, we had about 15 users, and towards the end, we had five users.

Our usage was not extensive. We used it only for one project, which was the motor voter project. We don't have any plans to increase the usage. We have stopped paying the subscription fee from the last month because we migrated everything over to ALM Octane for our business requirements.

How are customer service and support?

We didn't need to call them at all.

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

We were using IBM DOORS Next Generation for business requirements. It was on-premises, and we weren't able to make it available through a URL to the external consultant or workforce. That's why we basically went with Jira. IBM DOORS Next Generation wasn't flexible enough to accommodate all of our remote workforce.

How was the initial setup?

It was straightforward and easy. You basically create an account for your department, and then you onboard your users. There is a subscription fee per user for each month through Confluence. 

It took us a week to get it up and running. It involved reading, studying it, figuring it out, and then doing it. It was pretty simple to set up data and add users. So, we onboarded it within a week.

The challenge for us while setting it up was that we had to put it on a credit card, which is not a good thing for the government. Typically, the government likes to pay through a purchase order or procurement process, but because it was a monthly subscription fee, it had to be on a credit card. We had to use an executive card in order for us to pay the bill every month, which was really kind of a pain because our accounting office always had to make sure and check the number of users. They would ask if I had 15 users this month. I am the administrator of the application, so, of course, I know how many users are there. I can see how many users are there and how many are using it and remove them if they don't. I think the state just needs to modify its procurement process because I think ours is pretty old school. I don't think that Atlassian needs to adapt to ours, but that was the only challenge we had in setting it up and configuring.

What about the implementation team?

We had an in-house as well as a procured consultant, but he was through the state, not directly with Jira or Confluence.

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

The ballpark figure is about $100 a month.

What other advice do I have?

It is easy to use and easy to onboard. It has got a good foundation of offerings for the business requirements if you're working on an agile project or user stories.

I would rate Jira a seven out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Project Manager at Birlasoft IndiaLtd.
Real User
Offers more visibility and transparency, and helps to keep track of progress
Pros and Cons
  • "Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress."
  • "The solution lacks integration with visualization tools like Power BI or Tableau, which would be beneficial for better insights."

What is our primary use case?

I use the solution for agile project management. We use it to break down the project into tasks. 

What is most valuable?

Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress.

What I find most valuable in Jira is overall architecture, especially the ability to create dashboards. This feature allows me to gain insights into my projects.

Jira's reporting and analytics features have been super helpful for me in managing my projects. I can easily generate reports and create dashboards to track progress. I can export data to Excel, making it easier to work with outside Jira. The filters in Jira also make it simple to get exactly the data I need.

The tool has been really helpful for our remote team, especially with all our scrum events like daily stand-ups. Having Jira right there during those meetings helps us discuss tasks and settings easily. Plus, it integrates with Microsoft Teams, which we've found handy. It gives us a clear picture of what everyone's working on, so if there's a lack of progress on something, we can quickly address it through Slack or a call.

What needs improvement?

The solution lacks integration with visualization tools like Power BI or Tableau, which would be beneficial for better insights.

For how long have I used the solution?

I have been working with Jira for three years. 

What do I think about the stability of the solution?

I haven't experienced any performance issues with the product.

What do I think about the scalability of the solution?

Currently, our project has a team of around 40-50 people, plus additional members from the client side who are using Jira. It is scalable. 

How are customer service and support?

I haven't needed to escalate any questions to Jira's technical support. Whenever I've had doubts or needed help with something, I've usually found answers in the Jira community. 

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

Compared to Microsoft Azure DevOps, Jira is more user-friendly. It offers helpful video tutorials and other features that make it easier to use. One thing I appreciate about Jira is its ability to create and customise reports and dashboards.

How was the initial setup?

Setting up Jira was straightforward. The online videos guided me through the process. The program is more about automated deployment, not manual deployment. I wasn't directly involved in the deployment process. Usually, it's handled by the Jira administrator. I mainly focused on my role as a project administrator within Jira.

Maintaining the tool is easy; there's no problem with it. You can even add things from your Excel sheets into Jira. For example, if you have user tasks in Excel, you can easily upload them.

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

Our client handles the licensing aspect. They have not yet purchased the premium version. 

What other advice do I have?

We plan to integrate the tool with AWS. I rate it an eight out of ten. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Jira
March 2025
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Sweta Purvey - PeerSpot reviewer
Python Developer at Crosslynx
Real User
Top 10
An affordable tool with an easy initial setup phase
Pros and Cons
  • "The product's initial setup phase is easy."
  • "Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required."

What is our primary use case?

I use Jira in my company for my projects or the tasks assigned via the tool. I also use Jira as a scrum tool.

What is most valuable?

The solution's most valuable feature is that I used the tool to deal with bugs. In my project, with the bug assigned to me by my company, I was given the backlog and the code. Whenever I had to add it, I used to request Git for code push, pull, and merge, and then I used to paste that GitID into Jira. It was very easy for the other developers to handle whatever code I did.

What needs improvement?

At times, I am not able to report a bug. Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required.

For how long have I used the solution?

I have been using Jira for two years. My company is a customer of the tool.

What do I think about the stability of the solution?

It is a stable solution. Stability-wise, I rate the solution a nine out of ten.

What do I think about the scalability of the solution?

Scalability-wise, I rate the solution an eight out of ten.

With the latest versions being released, I feel Jira is being improved daily.

My previous organization used Jira, and now, my current company also uses it.

How are customer service and support?

The solution's technical support needs just to understand the customers' environments and improve or provide a better version of the tool. I rate the technical support a nine out of ten.

How would you rate customer service and support?

Positive

How was the initial setup?

The product's initial setup phase is easy.

The solution is deployed on the cloud.

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

It is an affordable tool.

What other advice do I have?

From a project management perspective, my project manager assigned some Jira tickets, and I started to do it on a weekly and daily basis. I send a request to a Jira ticket to open it, and during the process, I start describing how I am replicating that issue, explaining it in that Jira ticket. After that, I resolved that Jira ticket put that Git code in the expression part, and submitted it.

Regarding reporting and analytics features, my company uses Jira for software development projects as if it were a single tool. My company uses the tool in a manner where we send requests to one developer, and they open a Jira ticket using the email. Every day, they update so that everybody is able to see it without any description, while my team can see what the developer is doing daily. If a developer is updating, everybody can see that in the company. The tool is very easy to use, and it is easy to understand areas like script planning, story points, and backlog grooming.

I recommend the product to those who plan to use it. I worked with two scrum tools. In Azure also, my company uses scrum, which is a little bit uncomfortable for me, but I am very comfortable with Jira, a major reason I suggest it to other people.

I rate the overall tool a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Styliana Araouzou - PeerSpot reviewer
Senior Operations Analyst at Etoro
Real User
Easy to set up with great documentation and 24/7 support
Pros and Cons
  • "It includes by default all the necessary tools for a project manager to work and make their work more efficient."
  • "The reporting tool and the approval tool need work."

What is our primary use case?

I use Jira for project management. I track all my projects through Jira, including the resources, the time, the deadlines, or the roadmap. For me, it's the tool to check the status of the project. If we have time to get more people on the team, we can use it to show the up-skilling and the availability of the team.

What is most valuable?

They offer 24/7 support.

It's easy to set up.

There's lots of documentation to help you learn about the solution and troubleshoot issues.

The stability has been great.

A company can scale Jira if it needs to. 

It includes by default all the necessary tools for a project manager to work and make their work more efficient.

What needs improvement?

The reporting tool and the approval tool need work. The basic reporting tool includes only a few basic reports. If you need an advanced report you need to download a specific plugin, install it, and customize your reports on it. Sometimes you need to know SQL, let's say, in order to get the reports. It's not user-friendly.

With the approval tool, it's complicated in order to create the flow in Jira in order to achieve the approval process among different people. That needs to be simplified.

For how long have I used the solution?

I've been using Jira for almost now seven years. I have used Jira from 2015 until now.

What do I think about the stability of the solution?

It's a very stable solution; we've had no problems at all with that. There are no bugs or glitches. It doesn't crash. It's reliable. 

What do I think about the scalability of the solution?

The product is quite scalable. If you want to expand it, you can. 

We have hundreds of people on the solution in our company currently.

How are customer service and support?

I've used customer support in the past and have found them to be helpful and responsive. 

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is not complex. From what I understand, it's an easy setup and it's straightforward. They have a lot of user manuals as well, and they have also 24/7 support across different countries if you need help at any time.

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

While there is a cost associated with the solution, and licensing needed, it's not an aspect I deal with directly. 

What other advice do I have?

I'm not sure which version I am currently using. the admin team handles the versions and updates. 

I'd advise new users to read the user manual first, before jumping in. They are really helpful and informative. 

I would rate the solution at a nine out of ten. It is one of the best tools that I have used. It's helped me a lot in my daily job. For me, it's the best tool in order to track teams and projects. 

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Mitch Tolson - PeerSpot reviewer
Director of Robotics at Fresh Consulting
Real User
Great for managing backlogs, moving around tasks, and bringing structure to projects
Pros and Cons
  • "The solution provides users with clarity in terms of the scope of work in a given timeframe."
  • "There's a really steep learning curve for configuration."

What is our primary use case?

We basically use the solution for trying to develop a product end-to-end. It's assisting us in having hardware and software come together.

How has it helped my organization?

The solution provides users with clarity in terms of the scope of work in a given timeframe.

What is most valuable?

Managing the backlog and being able to move work around and drag it around in order to replan it to certain sprints is the solution's most valuable aspect.

What needs improvement?

There are many areas where improvements can be focused.

There's a really steep learning curve for configuration. I'd like them to simplify all of their configurability yet not remove the configuration options.

For how long have I used the solution?

I've been using the solution for two years.

What do I think about the stability of the solution?

We haven't had any noticeable stability issues. There are no bugs or glitches. It doesn't crash or freeze. it's reliable. 

What do I think about the scalability of the solution?

There are some issues with scaling. It's difficult to consistently configure multiple teams within a single product.

We have about 150 and they're robotics engineers, software engineers, firmware engineers, PMs, and product people. Anyone that would be on a product development team uses it.

We will maintain usage and intend to continue using it for this deployment. I cannot speak to if there are plans for expansion.

How are customer service and support?

We've never reached out to technical support. I can't speak to how helpful they are. 

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

I'm also familiar with Azure DevOps, which is easier to set up. However, this company has always used Jira.

How was the initial setup?

The initial setup has a moderate amount of difficulty. It's more complex than, for example, Azure DevOps. I'd rate the process at a three out of five.

The deployment took about three months. 

I'm not sure how many staff are needed for deployment or maintenance tasks. 

What about the implementation team?

We handled the implementation process in-house with our own team. We didn't have any consultants or integrators to assist us in the process. 

What was our ROI?

It's hard to put a number to the ROI we're seeing. It's more qualitative around the structure it provides than any kind of cost savings. 

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

The cost is about $10 per user, per month. 

There is a perception with Jira that they try to nickel and dime you quite a bit.

For example, they'll often say "Oh, you want this little feature? We'll charge you $3 per month per user." Whoever's signed up to your account they will charge you, even though you might only need five people to sue it from a 150 person team. That's excessive.

Compare that to Azure DevOps where withAzure DevOps, you just pay $20, and then you deploy that extension to your instance or tenant. With Jira, they charge you a dollar or $2 per active account in your tendency even if not everyone in my tenancy needs to have that extra feature set.

What other advice do I have?

Since we use the cloud, we are using whichever version is currently deployed there. It's updated automatically.

I would recommend Azure DevOps over Jira.

I'd rate the solution at a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1407036 - PeerSpot reviewer
Senior PM / Scrum Master at a financial services firm with 1,001-5,000 employees
Real User
Stable and easy to learn with good customizations, useful burndown charts, and support for a query language
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 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 regulatory reports as much as possible. I talk to our stakeholders to ensure that any errors in credit ratings are dealt with in a timely manner. A lot of these requests are ad hoc, and we prioritize them in sprints in Jira. 

What is most valuable?

It was very easy to learn Jira. I can't explain how easy it was. The hardest part of my job is understanding the business and communicating with difficult stakeholders and difficult people on the squad who are resistant to change and agile methodology. The fact that Jira was so simple to understand was a huge boon in my book because I didn't have to waste time trying to learn the tool to get work done and move the squad along. It was very easy to understand.

As a scrum master, I run daily stand-ups, and they are run directly from Jira. During these stand-ups, to make sure that there are no impediments, I run through all of the open issues and action items that the team members have. 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 am able to call each assignee and have them walk through the status of what they did yesterday, what do they plan to do for the next 24 hours, and if there are any blockers or impediments.

I also use Jira is for burndown charts. A burndown chart provides a visual depiction of how quickly the squad is closing out user stories. It gives us an indication of how efficiently the squad is performing. I also use the Active Sprints function and a feature called Planning Poker. Planning Poker is an add-on, and it allows me to work with my squad members to estimate the complexity of user stories. It allows me to estimate user stories in an unbiased way with my squad members. It is important that people are not piggybacking on other people's estimates, so when a business requests a functionality, I use Planning Poker to have people send me their estimates in an unbiased way. They cannot see what other people have estimated. This way, they have their own unbiased view on specific user-requested functionality and its worth. After that, we end up talking out like, "Why did you think it was a three? Why did the other person think it was a five?" So, it allows an unbiased way of estimating user stories.

What needs improvement?

One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. In Issue Navigator view, Jira allows you to enter JQL, which is basically like SQL. You just enter a query, and it displays the stories that satisfy the query. There is a field called Epic Link, which is basically a high-level designation for a bunch of user stories with a common goal. Epic Link is typically of different colors. When Epic Link's background color is a dark color, it effectively becomes unreadable. I am looking at my screen right now, and there is an Epic Link called Click View User Request. The background is purple, and the text is black. It is almost impossible to read it unless you click on it or give it an extra minute of viewing. That's basically what needs improvement. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view.

I've been required to report on metrics, and I don't know if it is possible with Jira, but there needs to be an easier way to capture a few metrics. For a two-week sprint, we are required to report on a number of metrics such as committed, completed, added, and rolled over. There is a way to see the stories that have been added after the sprint has begun, but there is no easy way to aggregate this, which is a waste of time. 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. There should be an automatic aggregation of how many story points were added after the sprint began and how many story points were rolled over to the subsequent sprint.

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. Typically, there is an established capacity for each sprint. I take an average of all of the delivered story points from the past six sprints, and I use that number to estimate how many story points can the squad deliver. I wish there was an indicator in Jira that tells you that you are approaching the number of story points that can be delivered during the 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. I can then talk to the squad members and say, "Okay, we need to remove some story points from the sprint because we're reaching capacity."

For how long have I used the solution?

My experience with Jira is pretty extensive. I pretty much use Jira every single day and multiple times a day. When I'm not using Jira, I'm using Confluence. I also use SharePoint.

What do I think about the stability of the solution?

It is 100% stable. Stability is also dependent on a lot of factors. Jira has been down once or twice, and people go crazy. In almost two and a half years that I've worked here, Jira was down only a handful of times, and I don't think that was Atlassian's fault. Atlassian is the company that is responsible for these tools. 

What do I think about the scalability of the solution?

I am not really aware of things in terms of expansion. However, there are some add-ons or extensions for expanding the functionality of Jira. The Planning Poker tool seems to be an add-on. Similarly, there is also another extension or plugin called Structure that was previously going to be leveraged. We haven't moved forward with that because we're using more of a manual solution in the metrics reporting. There is another add-on called Dataplane Reports. So, scalability is definitely there, and there are definitely opportunities to scale horizontally and expand the functionally of Jira through plugins and add-ons. 

In our organization, we only have 5,000 employees, and probably 70% of the company is using Jira. which includes the business as well. The business is also learning how to use it, and they understand that it is a very powerful tool. I would say about 3,500 out of 5,000 people are using Jira.

How are customer service and technical support?

I didn't have to contact Atlassian. We have an internal Jira support team that answers all our questions. I don't think they have contacted Jira support in a while.

How was the initial setup?

Its initial setup was not done by me.

What about the implementation team?

Its initial setup was done by Jira administrators.

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

I am not sure about the pricing, but I know its licensing is on a yearly basis.

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 jumping in. Try to talk to senior management and figure it out. You should learn how to read the burndown charts to basically understand how efficiently the team is working. Every organization has an IT organization, and I am sure the majority of them are using Jira.

I would rate Jira an eight out of ten. No tool is perfect, and there is obviously room for improvement.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Scaled Agile Consultant at Anthem Blue Cross Blue Shield
Consultant
Great story maps, an excellent overview of team performance, and very scalable
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 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 using programming preventative planning. We do it every three months.

All of the stories are tracked. We have a workflow defined and we have statuses defined. As the team works on the story, the story moves from one status to another and we close them when everything gets carried over to the production release.

What is most valuable?

The workflow is the most valuable aspect of the solution for us.

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.

There are excellent reports that come out of the data for every sprint so that you can do metrics on each. You can measure how the team is performing with respect to burn down charts, or with respect to how many story points were produced, or how many stories were moved out. For this, you can gauge the performance of the teams very effectively.

What needs improvement?

The solution needs performance improvements. We see that a lot of times it's clocking whenever there's any abuse.

When we switch from one view to the other, it takes some time before that view is presented. The performance for different dashboards, whenever they are loaded, it takes more time than you're comfortable with. Whenever you move from one dashboard view to another dashboard view, then it should come up quickly. Right now it takes a long time and sometimes it clocks. The overall product performance, whenever you switch a view is what they need to work on.

Whenever you edit a story, whatever you have changed takes a bit of time to save.

The integration between Jira and Jira Align needs to be better. There's a lot of differences between the two systems. I believe what happened was Jira bought this software from a different company called AgileCraft. And that integration is still in process, and, because of that, there's a lot of differences between the statuses. That sometimes creates a lot of confusion for senior management whenever they're reviewing performance across teams. Better integration between Jira and Jira Align is on the top of my "most desired upgrades" list.

The solution should improve performance when there are multiple users.

For how long have I used the solution?

I've been using the solution for about seven years now.

What do I think about the stability of the solution?

Whenever you load different views, it takes time. That's the only major issue. I didn't see any major glitches due to the fact that Atlassian is really good at catching them. The stability of this product is really great. I've been using it for, as I said for six, seven years now. I'm never unhappy with it.

What do I think about the scalability of the solution?

Our entire company, whenever there's a new division that goes into the agile mode of developing software, brings on Jira.

It's really scalable, however, at the same time, you need to really throw hardware at it to offer better response times when you add users. That goes without saying for most of the software.

We currently have 2,000 users on the solution. We plan to continue to increase usage in the future.

How are customer service and technical support?

We have an internal tech support team for Jira. We contact them whenever we run into issues. We have a platform for IT tickets. We use that to call them. I haven't directly called Jira Atlassian at any point, so I can't speak about their direct technical support.

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

I have used other packages for agile project management.

How was the initial setup?

I wasn't involved in the initial setup, however, we have a Jira administrator and they have a group, and that handles it. I implemented Jira for my teams. I added users to roles on the system. Roles such as developer, administrator, approval, managers, etc. That is all done by myself. In terms of that task, and setting up a project, it's fairly easy.

Implementation is a multi-year process. Right now, the whole company is on Jira. Whenever there's a new group, it gets added, and a new team is created. It's always a work in progress and it's not very time-consuming.

I would say the training of people on how to use Jira effectively takes some time. It's very intuitive, however, at the same time, a little training goes a long way in utilizing the software in a much better manner.

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.

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.
PeerSpot user
Software Engineer at Daum Communications
Real User
Top 10
Integrates comprehensive workflow tools and has advanced dashboard management

What is our primary use case?

I use Jira in many cases when developing software. For example, I often use it for gathering software requirements, checking management, and issue tracking. Sometimes, I use it for planning my software development. I create some pictures and activities for my software planning, so I usually use Jira for my entire software development life cycle.

How has it helped my organization?

Jira is very useful for us, so we can set the resource and time because Jira gives us some dashboard. We can track and manage the due date of issues using Jira. It allows us to check the project status by using the Jira Dashboard.

What is most valuable?

There are many features in Jira. Our team uses Kanban and Sprint from Jira. It is very convenient to connect Jira with Teams and Slack. Jira's integration with our workflow is deep, and we rely on it heavily for software development. Jira's ability to streamline processes is crucial. It's a user-friendly tool that supports many kinds of APIs, and we can easily create dashboards.

What needs improvement?

Nowadays, AI is a very dominant function. I would like Jira to adapt AI functionality, which would be useful for finding issues or the status of the development plan. If AI functionality were integrated, it would provide useful features like searching for types of issues within Jira.

For how long have I used the solution?

I have been working with Jira for eleven years.

What do I think about the stability of the solution?

Sometimes, there is a problem when Jira needs to sync data. During these times, we have to wait and can't use Jira. Although this kind of work is usually done over the weekend, it can cause trouble if we need to work during that time. After syncing, some errors occur but very rarely.

What do I think about the scalability of the solution?

As a user, I find Jira to be a very scalable tool. We have no problems when using Jira, indicating it is quite scalable.

How are customer service and support?

I usually ask for help from my colleagues. I do not contact Atlassian or their support directly.

How would you rate customer service and support?

Positive

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

I used Polarium before Jira, but I did not like it. I find Jira to be more user-friendly, with many types of APIs.

How was the initial setup?

Our team makes tools using Jira API. It supports many APIs, so we can create our functions and tools. Overall, I'd rate the initial setup experience as an eight or nine from one to ten.

Which other solutions did I evaluate?

I have evaluated Polarium before.

What other advice do I have?

I recommend Jira for project management. It is very convenient to manage issues or product plans and supports many kinds of APIs. It's easy to create dashboards. Overall, I would rate Jira nine 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.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.