Head Section Mobile Developer at a manufacturing company with 10,001+ employees
Real User
Top 5
Useful in project management and tracking but improvement is needed in integration
Pros and Cons
  • "We use Jira for project management and tracking."
  • "I want the tool to integrate connectors."

What is our primary use case?

We use Jira for project management and tracking. 

What needs improvement?

I want the tool to integrate connectors. 

For how long have I used the solution?

I have been using the product for five years. 

What do I think about the stability of the solution?

Jira is stable. 

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

What do I think about the scalability of the solution?

The solution is scalable. My company has 300 users. 

How was the initial setup?

Jira's deployment is easy. 

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

The tool's pricing is reasonable. 

What other advice do I have?

I rate the product a nine out of ten overall. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Agile and DevOps Coach at Infosys
MSP
Top 20
Good user interface, functionality expandable using plugin system, and it helps us track Agile projects at the initiative level
Pros and Cons
  • "The most valuable feature is Jira Align, which is a plugin that helps you to understand the progress that is made against each epic."
  • "Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate."

What is our primary use case?

We use Jira for project management.

How has it helped my organization?

Our team really needed something to help us track the progress that is made against our system-level requirements, and this solution helps us in that regard.

What is most valuable?

The most valuable feature is Jira Align, which is a plugin that helps you to understand the progress that is made against each epic. I have had limited exposure to it but by using Align, we can also see the progress concerning Initiatives, including progress made against the requirements.

In general, Jira Align is very useful for management. It allows them to see the big picture and what is really happening from a team-execution point of view. Being able to see progress against their Initiatives is a nice feature.

The UI is good, and it helps us to see what needs to be done to complete our sprints.

What needs improvement?

Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate. Jira should understand that at the leadership level in an organization, such as the C-level or even below that, they don't like to have an epic creator. Rather, they are interested in observing all of the corporate objectives that are being turned out by the team.

OKR is a very important feature for them to add, and it's a big investment. There are separate tools that are trying to support and enable people to use this framework. If Jira could do that, it would be great because we don't want to integrate multiple tools. For example, we don't want to use one for OKR and another one for Agile backlog items. If we can have support for everything using one tool, it would be helpful. That said, it would require a big investment to implement.

The biggest drawback that Jira has is that they don't have a separate chart to show metrics for lead time, cycle time, and throughput. We use the control chart as a workaround but it's not giving us the correct metrics. The metrics are skewed because the chart shows us some items that are still in an open state. This is something that needs to be fixed. By comparison, Rally Software has a feature that enables people to understand the lead time, cycle time, and throughput as separate metrics in different charts. Having Jira implement that capability would be helpful.

We are unable to enter an explicit agreement below the kanban board, which is something that we would like to be able to do.

For how long have I used the solution?

I have more than five years of experience with Jira.

What do I think about the stability of the solution?

Stability-wise, Jira is good.

What do I think about the scalability of the solution?

Jira has no problem with scalability. It's far better if you compare it to Rally.

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

I also use Rally Software. Some times are more on Rally, whereas other things are more on Jira.

Rally software has some better charting features, whereas Jira is more scalable.

Between these two products, it's very difficult to say which I would recommend. Rally has some good features that are not available in Jira. For example, in Jira, we can't put an explicit agreement below the kanban board. This is something that we can do in Rally. Rally Software, on the other hand, does not have the feature that allows us to understand the progress made at the feature level or the initiative level. This is something that Jira gives us with the Align plugin.

I would lean toward Jira as the market leader. If they improved some features, such as the metrics available on the charts and support for OKR, I would prefer and recommend it over Rally and other products.

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

The pricing for Jira is reasonable, although I think they can bring it down because the plugins cost extra. Jira Align, for example, is available at an additional charge.

Jira should understand that there are now competitors in the market, and they should lower their prices to expand the user base. As sales volumes increase, the price should naturally be brought down. In this case, people are more likely to retain their licenses instead of switching to a more cost-effective solution.

What other advice do I have?

I would rate this solution 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 2024
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
765,234 professionals have used our research since 2012.
Director Of Technical Project Management at a healthcare company with 10,001+ employees
Real User
Top 20
Highly customizable and helpful for dynamic communication
Pros and Cons
  • "The dynamic communication and the ability to customize it the way we want are the most valuable features."
  • "Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."

What is our primary use case?

Its use case just depends on the company I've been with at the time. I have used it for defect management, development processes, and status. At one point, we ran our entire risk platform out of it as well.

What is most valuable?

The dynamic communication and the ability to customize it the way we want are the most valuable features.

What needs improvement?

Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon.

For how long have I used the solution?

I have been using this solution for about eight years.

How are customer service and support?

I have not interacted with them. I've struggled with getting Atlassian resources, but that could partially be my fault.

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

It depends on the type of license. In terms of subscription, it is cheap, and it works pretty well.

What other advice do I have?

You need to investigate and understand dynamically what it is that you're looking to do. Don't just dive in and start creating. Before going into it, you should really organize your formatting or direction of the cause. There are other tools that are like cookie-cutters. Jira is so customizable that you really need to define what you're going to do with it.

I would rate it a nine out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Software Engineer 2 at a tech services company with 10,001+ employees
Real User
User-friendly with great bug and tracking capabilities
Pros and Cons
  • "It's easy to escalate the issues to the product development team."
  • "In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team."

What is our primary use case?

The solution allows us to escalate issues from the end-user customer very easily. For example, if they're trying to access our PayPal page, and they're getting an error, we will do the basic troubleshooting. If the problem persists, then we will file the case and we will send all the stuff to reproduce the issues, including the ID, everything, using the Jira tool. We will create the task and it will go to the Level Three engineering team. They'll create that bug and route it to the Product Development team. Since the time I've raised the ticket, there are lots of options and there are lots of products that we may be using. That includes understanding what is the issue, what is the SLA, what is the issue criteria, et cetera. We can create and submit issues based on multiple types of criteria.

How has it helped my organization?

I can collaborate on issues that I've escalated very easily, even if they were escalated to different groups. I can segregate as well. It makes it easy to track bugs and issues. 

What is most valuable?

My experience with Jira has been great. Jira can track bugs and records improvements clearly. 

It's easy to escalate the issues to the product development team. 

It's not that difficult to create and file an issue. It is very user-friendly.

The ability to include attachments and assign reporters is great. We're able to easily delegate the task. That's extremely helpful. 

In every email, there is a way to track who is looking at a specific issue. If you look into Jira, there will be a crystal clear communication chain from the start to end of any issue.

What needs improvement?

In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team. Or, for example, if you're sending a Jira ticket to me, I should get an alert if I've not worked on the ticket for a long time. I should always get an alert within 24 hours. For example, there should be three kinds of alerts. If a Jira ticket is raised and does not have any steps, for example, if I'm not assigned, it should be in green. If one day goes by, it should be in yellow. If the SLA is about to end, it should be in red. That way, I will know what needs to get attention. I'd be able to say "Oh, I should work on my task." There should be some color-coded alerts to keep me informed in a more visual way.

Sometimes I might get an attachment from the user through email that I need to download and save to my local desktop. What feature I would like from Jira is the ability to have an attachment field option open Outlook. Right now, when you click an attachment, you can only attach the items which are stored on your desktop or documents that have been downloaded. However, there should be an option to attach a file to a Jira issue directly from Teams or Outlook.

They should offer free online training courses to users. 

For how long have I used the solution?

I've been working with this solution for seven years. While I joined the organization seven years ago, the company had already been using Jira for quite some time. 

What do I think about the stability of the solution?

The stability is good and the solution follows the agile methodology. We've never had issues with its reliability. There are no bugs or glitches. It doesn't crash or freeze. the performance is good. 

What do I think about the scalability of the solution?

It's my understanding that the solution can scale. 

We have more than 5,000 people using the solution right now. They include IT specialists, product support, developers, product owners, technical lead, and architects.

How are customer service and support?

I have not faced any Jira issues. I have not raised any tickets to the Jira team directly. It works very well.

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

The company may have previously used ServiceNow, however, as I recall, it is difficult to expand, and therefore the company has used Jira for quite a long time. 

How was the initial setup?

I'm from technical support. I'm not a part of the development team and therefore have not helped implement the solution. Therefore, I cannot speak to how easy or difficult the process is. 

Jira maintenance is taken care of by the product maintenance team and the change management team. While we own the product, they respond to it. 

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

I'm not aware of the pricing or costs. It's not an aspect of the solution I deal with directly.

I am aware, however, there is a bit of a cost to do the online training.

What other advice do I have?

We are using the latest version of the solution. 

You can use both cloud and on-premises deployments. Cloud deployments can be on various clouds, including Amazon, Microsoft Azure, et cetera. We are using GCP, for example. 

I'd rate the solution at a ten 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?

Google
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Software Engineering Manager at a comms service provider with 10,001+ employees
Real User
Stable, good technical support, but more reports needed
Pros and Cons
  • "I have found Jira to be scalable."
  • "We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface."

What is our primary use case?

We are using Jira for ticket management.

How has it helped my organization?

The solution has helped my companies efficiency with managing tickets throughout the life cycle.

What needs improvement?

We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface.

The solution could improve the Agile reports. They do have quite a bit of reports already, but additional reports would be a benefit.

For how long have I used the solution?

I have used Jira within the past 12 months.

What do I think about the stability of the solution?

Jira is stable.

What do I think about the scalability of the solution?

I have found Jira to be scalable.

We have a few hundreds using Jira in my organization. They consist of developers, project managers, and testers.

Whether we increase usage of the solution depends on what each team wants to do. There is some level of common solution approach, but I don't know for sure whether this is the direction that everybody is wanting to adopt.

How are customer service and support?

We had to reach out to their support a few times. The support was good, I did not have any issues with them.

How was the initial setup?

The initial setup was not difficult.

What about the implementation team?

We have an IT team that supports the solution.

What other advice do I have?

My advice to others wanting to implement this solution is to utilize the SaaS solution unless it is required not to. Having your own instance running in your data center or private cloud requires your own staff and resources to maintain and upkeep. It can be quite time-consuming work. Unless you are invested in something like that, there is a benefit of just using a SaaS solution.

I rate Jira a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Oracle Applications Consultant at ASAM Conseil Inc
Real User
Top 20
Integrates with other products easily
Pros and Cons
  • "I've never had a bug or a bug message that I needed to open a ticket for."
  • "It should be connected to ServiceNow."

What is our primary use case?

I use the Jira app, not the desktop version. 

I work at a university and we use Jira to create tickets, epics, and stories. We link Jira to spec documentation with Confluence. We can also link it to TestRail.

Within the university that I work for, there are roughly 4,000 people using this solution — all staff members use it. 

What is most valuable?

I like that it's integrated with the specs. You don't have to put the specs in a shared folder or a shared server. It's all linked together with Confluence. We just put the specs into Confluence and then link it to the ticket in Jira. Once our developer has finished his development, we can link it to TestRail to create test scenarios, test them, and analyze the results of the test.

What needs improvement?

It should be connected to ServiceNow. We use ServiceNow for deployments from our test environment to QA, then to production. If it was linked to ServiceNow, it would be perfect — it would be more integrated. Still, at least we can link our test scenarios, specs, and the tickets themselves so we can track the requirements — that's good. We have to use ServiceNow separately to deploy and move corrections from one environment to another.

There are a lot of features that need to be added on top of Jira for management, sprint planning, and agile topology for project management. My project manager says that there are not a lot of features for project management in the agile mode. They have to buy other products to put on top of Jira to be able to properly manage and to track what people are doing.

For how long have I used the solution?

I have been using Jira for two years. 

What do I think about the stability of the solution?

I was always able to connect. Once you're inside, it's good. We have never experienced any bugs, glitches, or crashes. 

What do I think about the scalability of the solution?

I think it's scalable. It can be integrated with other products easily. It's not a standalone product. Integration is the most important thing when it comes to scalability. I believe it uses a certain technology to make it even more scalable. 

How are customer service and technical support?

I've never had to contact support. I've never had a bug or a bug message that I needed to open a ticket for. 

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

We used to use Remedy, but it didn't have everything that Jira has. Jira supports agile methodology. I used Remedy with waterfall projects, but for agile, Jira is the way to go. I've heard people say that Jira is better than DevOps tools.

How was the initial setup?

I don't think it's complex to set up. The features are standard and come included with the product. You only need to know how to use it, create new Jiras, and how to link them. I don't think the setup is complicated. I've installed Oracle E-Business Suite a lot — that's complicated. Jira is much more direct. 

What other advice do I have?

If you're interested in using Jira, you have to just go ahead and buy it and use it. Try to use all the functions that are available. There's a lot of things to do in Jira. I recommend it. 

Overall, on a scale from one to ten, I would give Jira a rating of seven.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Testing Manager at Cloud Solutions
Real User
Quick and easy to customize
Pros and Cons
  • "The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
  • "There is a difference between their cloud and their server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it."

What is our primary use case?

We use Jira for multiple uses; project management, task management, and we are starting to use it for release management.

What is most valuable?

The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on. For these results, it is very helpful. I also like the customization that we had for the workflows for the different issues, it's quick and easy to customize. The reporting is also easy and the dashboards that they provide are really helpful and simple. It does not need a lot of experience with reporting and presentation to get to what you need. Also, most of the advanced reports that you need to create can be exported as Excel files.

What needs improvement?

I have been watching an issue develop. There is a difference between their cloud and their  server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it.

Additionally, it would be really nice if they added some custom reports so that you could build your own report through any open source or commercial plug-in like Crystal Reports. That would be much easier for them to accelerate. You can create a report template and use it frequently.

There are a few features I would like to see in the next release. For example, the layouts could be easier to configure on the screens. I know it's easy to customize. For each issue type you can create and modify your screen. But it would be easier if you could enlarge, copy, clone, and visualize them in a model in a visual way. It's really hard for me as an admin to compare different screens or even to copy one screen with one additional field. I believe that is creating a lot of confusion for end-users because usually admins are looking at each field independently, where it's located, in which position, and which screen. So that all needs to be improved from an administration point of view to make it easier to visualize and compare between the screens.

For how long have I used the solution?

I have been using Jira for almost a year now.

What do I think about the stability of the solution?

In terms of stability, it is fine.

How was the initial setup?

The initial setup is easy and straightforward. The deployment is very easy. It just took one server.

It took one day to set up the database and then start the configuration. That is straightforward. And I believe they have a newer deployment model that they can deploy on Docker and other container platforms.

What about the implementation team?

I did it myself with some help from other team members.

What other advice do I have?

Jira is an amazing tool, but to get the process streamlined is a challenge. So don't start from Jira. Start with your process first. Agree on the workflow, identify all the stakeholders, and then from there you can go ahead with Jira and implement anything.

On a scale of one to ten, I give Jira a 10.

Everything already provided is perfect. We are using Jira perfectly for one year now and it's absolutely great.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
JananiLiyanage - PeerSpot reviewer
Enterprise Agile Coach at Agility Tune Up
Real User
Contains helpful features like SAFe Agile and Sprint Reports, but traceability feature could be improved
Pros and Cons
  • "In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful."
  • "Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management."

What is our primary use case?

I am using Jira for some programming-driven planning and PI planning system, but I have just started using it for that. I am primarily using it for some projects.

I'm serving as an enterprise agile coach, so I work with a team to help them use Jira. I'm not really sure what the exact data subjects are, but I mostly look at what the team is doing and if they have updated, then they let me know. I'm not using Jira for my own instances, but for my team's. I'm helping the scrum masters and the product owners.

The solution is deployed on cloud.

What is most valuable?

In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful. With regard to SAFe Agile, I was looking at having a proper program board. So far, I have tried using the portfolio feature. Something that I have been looking to understand or learn more about is how to integrate Scaled Agile and their work types into the Jira.

What needs improvement?

I'm still exploring the solution. I think the knowledge is a challenge because most people are used to Jira for teams, but not Scaled Agile. I think that is an issue with awareness. We are looking for some YouTube videos and help pages on finding that. Maybe there are features, but sometimes we aren't aware of them. We are still in the exploration stage.

I would love to see transparency in terms of how the program is displayed when you are working in multiple teams, especially how the dependencies could be tracked. The most important thing at the moment is that it is easy to do.

Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management. If you can see the traceability nicely, that is also something that we are looking for. Today we can link and do things like that, but sometimes the solution has a bit of a challenge with attaching test cases, so I think we have to use some plugin. Traceability with the test cases could be improved.

For how long have I used the solution?

I have worked with this solution for five years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

I'm not able to comment on the scalability because I work with different types of teams. Some teams are really big, and they haven't said that they've faced any challenges. I haven't specifically asked, so I'm not very able to comment on that because I don't know for sure.

I'm working with a couple of teams made up of 20-30 users or 100-150 users, and maybe more for certain accounts.

How are customer service and support?

I haven't had a lot of experience with technical support, but for the questions that I have raised, I received a pretty quick response, so I'm happy with that.

How was the initial setup?

Setup wasn't that big of a challenge.

What about the implementation team?

Implementation was done by Jira administrators, which was good.

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

The license is yearly. It is a large, long-running program.

Which other solutions did I evaluate?

Some of my teams have been using Version 1 and Rally. Because of that, I have been exposed to those tools for some extent.

My experience is much more with Jira. That's why I tend to go for Jira, but we haven't used many other solutions. Based on teams and what the people are saying, they find Jira to be more user-friendly. For Scaled Agile, I have also heard that they have found certain features in Rally more useful. But I don't know, I haven't used Rally to that extent.

What other advice do I have?

I would rate this solution 7 out of 10.

Which deployment model are you using for this solution?

Public Cloud
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: March 2024
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.