Jira Reviews

We use Jira for the overall issue management in development projects. We use it to maintain a high level during each sprint, which is a requirement. We also use Jira for issue management during testing. We create a test plan and manage it all with Jira.

Jira is very user friendly, easy to install, and easy to access. The most valuable feature in Jira is release management. You can also manage a consolidated dashboard that can be accessed globally by all the team members. We can do all this with Jira while engaging in development. 

One of the key benefits is that it's a single repository for all your SDLC. Based on the user ID and password, anyone can access it, and they also have a single sign-on. It's not that very complicated to do issue management with Jira. We can also pull Jira data and generate quality metrics that can be used for the overall optimization of the test execution. 

Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature. Because right now, we're using third-party tools to test executions.

If there are multiple projects, it could be a good thing if they had a reporting method where you have a portfolio view with predictions and so on. If there were a way to manage all the SLAs, that would be helpful too. 

Jira is stable and meets our requirements. You don't have to use it out of the box as you can customize it to your requirements.

Scalability isn't a problem because we have used it with over 200 users. You don't have to stick to any out of the box features as you can customize them.

Almost everything is covered in their documentation. As payment is required for support, we mostly follow the documentation.

We used Microsoft DSP before. We were looking during a licensing phase for something where the non-licensing cost wouldn't be more, and the system requirement would be minimum. That's what qualified Jira, and we went with the data.

The initial setup is very good. I wouldn't say that it's very complicated. They have customization options for things like issue management. You can customize it based on your terminology and project.

For a simple set up, it may take around four hours. If it's a 20 member project, it's quite easy to set up Jira. But if it's to be made available enterprise-wide, it takes longer. I had complex projects where it took anywhere from three to four days or a week to set up. You should also note that it may take new users a week to understand it properly.

We tried to do a total uniform deployment, but it's not always possible because every project has some customization. A single user can deploy Jira. I have deployed and managed 20 to 22 users in a Jira instance. Basically, the Jira administrator creates the template. But if the project requires customization to write queries and run tests, that will require some additional skill.  

As a company, we get a subsidized price, and it's lower than what's quoted on their website.

To a certain extent, maybe 70% to 80%, Jira will meet your project development budget. It has integrations with other platforms, so if you want to put it in your DevOps continuous integration flow, it can be done.

If you're engaging in software development, there should be a single repository where you store everything. Then you can start managing it with Jira based on the business requirements and the user stories.

On a scale from one to ten, I would give Jira a seven.

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.

Our primary use case is executing the SDLC.

This solution has improved our organization by enforcing transparency and communication. Individual roles and responsibility are defined and followed.

The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards.

We have found that improvement is needed in their customer support (communication, which is ironic).

It would be very useful to have drag and drop time tracking.

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

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

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

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

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

Better user management features could help.

I have no problem with stability.

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

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

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

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

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

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.

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.

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.

Purchased Sept. 27th 2014.

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.

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.

The Premier Support team was very thorough and very responsive.

The Premier Support team was very thorough and very responsive.

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.

The initial setup was straightforward.

Yes, we have other vendors and tools – evaluation is ongoing.

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.

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.

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.  

I have been using Jira for approximately one month.

Jira has been a stable solution.

I have found Jira to be scalable.

We have 20 people in my company using Jira.

The setup of Jira was simple.

I did not compare Jira to other solutions.

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.

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. 

The integration could be better in Jira.

I have been using Jira for approximately 15 years.

I have found Jira to be stable.

Jira has been scalable.

There is an annual subscription to use Jira.

I would recommend the solution to others. I have been happy with Jira.

I rate Jira a seven out of ten.

We use Jira to create releases, tasks, sprints, and collaborate within teams. The solution can be deployed on both the cloud or on-premise.

Jira has a useful user interface and overall is easy to understand and learn.

Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure.

I have been using Jira for approximately eight years.

Jira's stability could improve. We have experienced times when we were out of memory which is possible due to a memory leak. It is hard to pinpoint the cause, it could be the operating system.

I have had to contact the support when I had some questions about the upgrading process and they answered in a timely manner.

I have previously used a comparable solution to Jira and the largest benefit was it was free.

The setup is not difficult. I have done it a few times in Kubernetes and did upgrades, the experience was straightforward.

There are other solutions that are free making this solution seem expensive in comparison.

I have found the cloud deployment better than the on-premise. However, for those wanting to implement this solution, I would advise them to compare the pros and cons of each before making their selection.

I rate Jira a ten out of ten.