JIRA Pros and Cons
It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it..View full review »
The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs.View full review »
We can cope with processes easily without adapting the tool, but adapting the tool to processes.View full review »
JQL, JIRA Query Language enables me to 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.View full review »
The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components.View full review »
It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasksView full review »
Transparency of development projects, as well as approval processes for some business projects, has improved massively.View full review »
Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on.View full review »
Some of the features that are most important to me of JIRA Agile are the sprint planning, being able to write user stories and being able to use task management.View full review »
This tool can be used anywhere and on any device.View full review »
I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be.
I would like to see visualization of release planning. I can list the releases and I can give dates to releases, but to show how they are happening on a timeline, I would need to order the Portfolio part. But just for this, it may be too much to use the Portfolio for that.View full review »
The plugin management needs a lot of work.View full review »
There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes.View full review »
I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.View full review »
There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level.
Sometimes, it is slow and hangs. We faced some stability issues where JIRA was down for a day. Also, we have lost some of our comments made in the JIRA because of downtime.View full review »
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.View full review »
JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless.View full review »
I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool.View full review »
The user interface and views on different devices should be improved.View full review »
I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.
I do know the initial setup was pretty complicated. The user interface could be better organized and easier. View full review »