Jira Reviews

We use Jira to manage scrum projects for the different projects in our company. Our business is a development company that uses the cloud version of Jira to manage the sprint and releases for each project for each client. We manage scrum and cascade projects with our clients.

Jira allows us to manage the project in a visual way, where you can easily see your sprint board and you see the status of your project, as well. It helps us to finish the sprint on time and easily move issues that are not finished to the backlog or to the next sprint. 

The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project.

The boards also help us to determine our velocity, and if we reach the release date it helps to determine which issues need to be moved in the event they will not be finished on time.

We would like to see the integration of a lite-version of Confluence, just to manage some of the templates and documents.

Without a plugin, implement the Route in projects created before this feature did so in the most recent versions of Jira.

I've been used Jira since 2016, and it helps us a lot.

I use this solution for general issue management, software planning, and change management.

This solution is a one-stop-shop for issues and plans.

Issue linking has enabled teams to trace issues.

I like the dashboards and Kanban boards.

The development links to GitHub are critical.

The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily.

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.

We use this solution for product development and issue tracking.

This solution provides us with a centralized view of issues, simple time registration, and excellent integration to Bitbucket.

The most valuable feature of this solution is the source linking on the commit level to git.

The speed of this solution needs to be improved.

Backlog pruning and visualization are poor. 

Uupdate:

Speed has improved slightly in backlog view with Jira 8.0, but there is still room for speed improvements.

It's difficult to group and manage the backlog and priorities on multiple simultaneous epics to get clear overview of how the backlog reflects a planned roadmap. (perhaps due to the fact that we have too many issues in the backlog)

We use this solution for our scrum team and user story management.

This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on.

This solution is very easy to set-up and use. It is very intuitive.

The permissions can be challenging to get right.

We use this solution for Agile project management and BAU work delivery in sprints / DevOps.

This solution has helped with team collaboration and task delivery.

The most valuable feature is the Burndown Chart to see work that is outstanding.

The reporting needs to be improved.

We use this solution for Agile Scrum-Based DevOps on AWS with a Linux, Cloud-Based SaaS environment for mission-critical applications.

JIRA has increased the transparency of DevOps and it has enforced systematic, process-driven, communication.

The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications.

This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number. I would like to see a more customized workflow, as well as support for the Google Doc storage of Documents.

Our primary use case is ALM, which is very well supported by Atlassian.

We have realized an improvement of 30% in terms of the duration of our small projects (six months with three to four people).

The most valuable feature is the full integration between Work management, Source code management, and Test Automation.

This integration allows a full traceability during the development processes, which is mandatory for some industries like automotive, or security

The hierarchy for Jira tickets is too flat.