Jira Review

User-friendly and provides very good visibility and traceability, but should have role-based access and more reports

What is our primary use case?

It is used by the agile teams for product development and feature management.

What is most valuable?

It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust.

It is working well, and there are a lot of add-ons or plug-ins out there that you can use. 

What needs improvement?

It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira.

I would like to have more reports in Jira. Currently,  eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports.

For how long have I used the solution?

I have been using this solution for five years.

What do I think about the stability of the solution?

It is stable. I don't see any instability in Jira.

What do I think about the scalability of the solution?

It is easily scalable. We have around 1,500 users.

How are customer service and technical support?

I have not directly interacted with Jira's technical support. We have an internal Jira service desk for any issues.

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

I have used HP ALM, version 11, and it was not so robust. I found Jira to be more robust. In HP ALM, you can define the requirements and test cases and map them, but you cannot see the in-depth requirements, whereas Jira provides more visibility, and you can see each and every part of a process very clearly. It is more open and user-friendly. 

Traceability is very important for the SDLC process, testing lifecycle, and audits, which is one of the key features that Jira provides. It provides detailed traceability so that you can easily know about the sprints and change requests. With HP ALM, you can define requirements only in one or two lines. It is more of a testing tool. It is not a development lifecycle tool.

How was the initial setup?

The initial setup for Jira was done by a third-party vendor, so we did not face any issues. The migration from an older application to Jira was not so easy, and it required a lot of effort.

What about the implementation team?

It was implemented by a third-party vendor. It requires maintenance, but it is not so difficult to maintain. For maintenance and administration, we have an internal Jira service desk.

You need to do upgrades because you tend to have requirements from different stakeholders. You also have different add-ons and plugins, and Jira also keeps on releasing new versions that might be useful.

What other advice do I have?

I would recommend this solution. I would rate Jira a seven out of ten because there are some areas to be improved in Jira.

Which deployment model are you using for this solution?


Which version of this solution are you currently using?

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Jira reviews from users
...who work at a Computer Software Company
...who compared it with Microsoft Project
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
521,817 professionals have used our research since 2012.
Add a Comment
ITCS user