Jira Reviews

We use Jira as a communication tool for tasks and epics. Everything is in one place in the ticket, and it's helpful to communicate with the team. We don't have to use Slack and other platforms to track information related to tasks.

The most useful features are the Kanban dashboard, the ability to create tasks, bugs, epics with child issues, time estimation, and Jira reports. The dashboard helps in tracking tasks and projects easily. Time estimation is crucial for my team to estimate tasks accurately, and the monthly reports are helpful for monitoring progress. We can see everything in one place, which improves communication within the team.

Sometimes it's hard to set up the dashboard for the team lead. For example, I can see tasks selected for development but not UAT tasks. It would be beneficial if the setup was easier. I understand Jira is a comprehensive tool, but dashboard setup could be made more user-friendly.

We've been using this solution for about two years already.

The stability of Jira is good. I have faced issues only once. I would rate it nine out of ten.

Jira is pretty stable and scalable. On a scale of one to ten, I would rate it nine for scalability.

I haven't contacted customer support yet.

Positive

My company also uses Azure DevOps dashboard. I prefer Jira because its interface is simpler and easier to use than Azure.

I am just a user of Jira. The dashboard setup is done by our team lead, so I'm not sure how to set up Jira.

The price is regular for this kind of tool. However, my company hasn't bought Confluence integration because of the price. We are fine with Jira, but would like to have integrations if it becomes cheaper.

Feel free to try it, and you will love it. The biggest advantage is that you can see all of the project in one place on the dashboard, track your estimation and time, and see your progress. I rate Jira nine out of ten.

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.

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.

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.

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

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. 

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.

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

Positive

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.

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

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. 

I am an Agile coach and consultant, and my clients use Jira to manage Agile teams, including tracking and gathering reports on performance at the team level as well as the team-of-teams level.

Since I work with different companies in my consulting work, there are different versions and implementations of Jira that I deal with. Most of the time I work with Jira on-premises, although I have worked a few times on the cloud edition.

In the near future, I most likely be using Jira Portfolio instead of the regular Jira because that will be my new responsibility.

I enjoy working with (and can recommend) Jira for a number of reasons. The best features are that it is friendly and provides good visibility. It's to the point and very effective.

When I start work with a company, one of the promises I give them is that they will get visibility, and very quickly at that. We are able to easily create boards and have the teams start work with story points. Then, we will make use of the Structure feature, which is another good feature that we get benefit from. 

In terms of the general Jira software, one element that is missing is budget management. Perhaps such functionality exists in add-ons, however. Once, several years ago, I tried to use one such add-on (the name of which I can't recall) but I dropped it because it was not effective enough. If we had this feature, I think we could provide the whole picture to top management.

I have been using Jira for about five years. 

It is stable. 

It's not scalable enough, in my opinion. To explain, I have a specific level of understanding of Jira so I am able to make specific customization to support activities at scale, but I don't feel like Jira is easily scalable out of the box. It's not always natural to scale up Jira without customization.

The technical support that I receive is not necessarily talking with any Jira support team, but rather it involves using the community's help from the internet.

On one hand, this avenue of assistance is quite good because I can often find answers there, but sometimes it's not enough. In these cases, Jira will ask to open a ticket and to vote on it so it gets priority. But it's frustrating because we might still not get answers, or we don't find anyone able to handle our issue for months or for years.

Overall, and for most problems, I think I have enough documentation so I can figure out what to do and how to do it. When compared with other tools, I think that Jira's documentation is clear.

I don't deal with licensing in my current consultant position.

For application lifecycle management, I can definitely recommend Jira and I would rate it an eight out of ten.

What I like most about Jira is that it's flexible. It has the flexibility to be configured for any company.

An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. the most popular is Xray, or you can add Zephyr.

An additional feature I'd like to see included in the next release of the solution is the check in and check out feature for the test assets.

My team and I are currently dealing with Jira.

Jira is a stable solution.

I find Jira scalable.

The solution is very reliable, so support is not contacted often, but they are responsive.

Deployment of Jira can be completed within a few days. The number of people you use for its deployment still depends on the company size, but on average, you can use from one to two people for deployment, per week.

I was able to evaluate Micro Focus ALM.

I'm at a professional service company, and I'm the manager, so I don't work with any solution, e.g. my team works with the solutions. My team works with Jira plus Xray, then Azure DevOps, and Micro Focus ALM.

Micro Focus ALM is a very powerful solution, because you can link from the requirements to the test plan and the test lab. In the test lab, you can aggregate the test cases that you want to execute, including defect management. You can incorporate all these into a release, and inside this release, you can have several execution cycles. I'm referring to the functions of all the assets, e.g. functional testing. Jira doesn't have versioning, compared to Micro Focus ALM, so you can have different and fresh versions of the same asset. You can do that using different names, but Jira is not as well-designed as ALM.

I'm rating Jira an eight out of ten.

We use it for project and sprint planning and day-to-day bugs. We also use it for documentation, engineering, and enhancements tickets and for creating the feeds, which are like new features.

We are most probably using its most recent version.

It has been very helpful for feature enhancements, release planning, and sprint planning. We have been using it for creating bugs, enhancements, and all the tasks for a sprint. It helps us in looking at the quality aspects of the product along with the volume, burndown rate, and a lot of other things.

As an engineer, I like that it provides you blocks to put in comments, code, etc. It helps in giving better information. 

It is very configurable, and we can do whatever we want. Jira dashboards are also good, and we use them extensively. We also use the tracking mechanism extensively. 

Another thing that I like a lot about Jira is that in the dashboard, you can plug the modules that you want. You can enable certain sections. For example, you can show trend history, open Jira tickets, etc. Some of the managers have created a dashboard for each engineer. So, it allows you to do all sorts of things.

There should be a way to look for specific comments. When we have thousands of comments on a Jira ticket, there is no way to look at the comments of a specific type. In the comments, if there is a way to put a tag, it would be helpful. For example, when there are a lot of lengthy discussions happening on a particular ticket, there could be a conclusion tag or something like that to indicate a conclusion. It would help in sorting the comments based on a certain category, such as conclusion. I should be able to tag a comment with something like ##dev_conclusion##, and someone looking at the comments should be able to expand all the comments and search based on this tag. Some of our tickets can go up to 100 or 200 comments, and it currently takes a lot of effort for someone to go through them. It would be good if there was a way to preview the comments.

We want Jira to be the single tool that people use. We lose a lot of information when working at the ticket level in Jira. We don't want to have discussions in Confluence and design docs somewhere else. Currently, we make some decisions outside, and we make some decisions in Jira, and there is no combined way. There should be a way to integrate documentation into this, and I should be able to directly update the documents. They can also incorporate a review mechanism for documentation. I should be able to assign a sub-comment to someone to say, "I'll respond to it," or I should be able to tag someone to say, "Can you please look at it?" We should be able to use a workflow. There should be some built-in intelligence where when there is a design document in a Jira ticket, the signoff should be done by certain people. Currently, the documentation is completely separate. If there is a way to get the documentation into this whole workflow, it would be useful.

I have been using this solution for seven or eight years.

Its stability is really good. There is no doubt about it. Sometimes, we have performance issues. That's mainly because a lot of people have standup meetings between 8 am to 9 am, and everybody is using Jira at that time. The number of connections is at a peak in the morning hours. If I was a Jira development engineer, I would be thinking about a mechanism to ease that. Other than that, it is pretty stable and reliable.

We didn't have any issues with scalability. We create hundreds of tickets every day. We have between 1,000 to 2,000 users across all departments. It is being used extensively, and its usage might increase.

I didn't have any contact with their technical support. We have a Jira maintenance team. We have a Slack channel, and if there is an issue, we send it there, and the team looks at it.

I'm not a part of the team that takes care of its deployment. We are a big organization, and I am an end-user of it.

I would advise having proper planning because you don't want to clutter your Jira. Without proper planning, you would go on creating a lot of labels and other things, which would be of no use. You need to do release planning and then accommodate things into Jira. 

A lot of companies have a separate release planning team, and then there is a separate Jira infrastructure team. All these teams should think and work together. Otherwise, everybody would be creating their own tags, which won't make sense. I might create a tag for daily bugs, and someone might create another tag for the same thing, which would result in cluttering.

I would rate it an eight out of 10. Jira is an amazing tool. There is no doubt about it. We have no thoughts of using any other tool.

I use Jira for the development of different versions of software, upgrading it from one version to another, and developing and collecting specs for the new versions.

I like that Jira keeps track of time and is good for how it organizes.

Jira has a lack of graphical interface that maps the different cases to the space or in the project. For example, if you have a project that has a big diagram of component systems, people, and use cases, each of those Jira cases usually can be mapped to a specific location. This can be enhanced by a curve set of Jira, or a curve set of screens, where you can map on which pieces of the project you were working on at that particular screen. When working on the left side of the diagram, or the right side of the diagram, you should be able to request all those Jira that are related to that part of the project.

If a system has ten different steps of data flow and the components are clear. You should be able to map those Jira cases to different steps in the process. This would show you how a field or component is related to a location in the diagram. The diagram then would show all the cases waiting to be done or already done.

Jira works too slow, especially when you are in a big organization with thousands of users. It is also too slow when integrating with other components like SVN or with a built system. I would like to see everything that Jira does is under have a second response time.

I have been using Jira for about one year.

Jira is a stable solution, other than planned downtime, it has no downtime.

Jira is integrated with other components in our system, like the build and release systems. 

We use internal technical support.

I would recommend that an organization implementing Jira ensure that someone gets training both at the developer level and the project manager level. The developer needs to know what needs to be done, what are the components and why are they there. The project manager should join the training and determine if there is a relation between multiple projects to see that they are really integrated well into other components of continuous integration and continuous delivery.

Because of the slowness, I would rate Jira an eight out of ten.

The primary use case of this solution is to manage work, to distribute work to the teams, and we use confluence as a SharePoint for documents and to use AgileCraft.

This solution is easy to work with. It's easy to understand, and easy to navigate. 

it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do.

In the next release, I would like to see better integration with other software. Many companies have a lot of peripheral systems. They have ServiceNow or they could have something else. How do they integrate your stories, your sprints, or if you have confluence, or SharePoint when you start using Jira? 

The challenge is when you have someone who is not using confluence, but they have SharePoint or ServiceNow.

How do we connect, or integrate our stories with Jira, so we don't have to have the information in three different places? 

The integration and integration threads would help Jira going forward.

I have been using Jira for more than one year.

This solution is stable. I haven't experienced any issues, it works fine.

We have approximately 100 users. It is not used concurrently. There could be anywhere from 20 to 30 users in a day.

We have yet to explore the scalability, but we hope that it is easily scalable. For us, that was the purpose of using this solution in our organization. We plan to use SAFe, a scalable scaler, scale agile.

I have not contacted technical support,

The initial setup was done by two local employees.

This an area that I would like to explore more from an admin perspective, on how to set up teams, what are all of the things we can do, and to set up the right way so that we can get the most potential out of the software.

I am not involved in the pricing. We have a sales team to procure our licenses.

I don't feel that price is an issue.

I have heard of many other solutions, such as Rally, but I have not explored it or compared it with Jira.

It's difficult for me to tell you everything that Jira has to offer when I am still learning. I am trying to educate myself to have a better understanding. I want to learn more.

I would rate this solution an eight out of ten.

We use JIRA for software development projects and the implementation of business workflows. Our company runs more than one hundred projects on a single instance server. Besides core IT projects, we have implemented business processes on dedicated JIRA instances to manage high volume (greater than five thousand issues per month) non-conformities for some business lines. 

Transparency of development projects, as well as approval processes for some business projects, has improved massively. Interaction of business units and IT happens very often via JIRA and considered to be very helpful. As many of our developments are requiring some level of compliance, the workflow and documentation of approvals are very handy. 

There is a very flexible configuration of "issues" and related life cycle. On top of it, the number of "add-ons" is overwhelming and of very good quality. I would consider the reporting capabilities to be the best feature, as ultimately the visibility of issues allows management of the projects.

My main concern is the administration of projects, especially user groups, and this requires root access rights but there is no concept of layered admin rights. Projects can be managed by a limited admin, but the creation of projects needs root admin rights. In decentralized project ownership, this gets tedious.

We used an open-source system called Mantis, which was considered unsuitable for use outside the IT world.

The setup of JIRA is straightforward.

To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money.

We went right away to JIRA without evaluating other options.

JIRA, its add-ons, and the Atlassian product world are already very powerful and it is difficult to name significant blank spaces.

This is a very powerful solution. Get some advice and training to make the most out of it. You may miss out on some of the capabilities if you don't.