What needs improvement with JIRA?

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

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.

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)

The permissions can be challenging to get right.

The reporting needs to be improved.

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.

The hierarchy for Jira tickets is too flat.

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 plugin management needs a lot of work. Sometimes you have issues with plugins and it stumps the vendors, as well as the Atlassian support. I think that more extensive reporting would be very good because sometimes it is a hassle for us.

The user interface and views on different devices should be improved. The customization feature can also be improved.

This product or software still requires improvements, especially in its interface since its learning curve is somewhat high because it offers so many features that the user tends to get confused, or the software adaptation time is much longer than it should be. Besides, its configuration is not very simple, and its support team sometimes does not respond immediately, so it is often necessary to solve problems on their own.

The downside to JIRA is the constant push for the changing of the user interface. This can remove valuable features and increase the learning curve. Especially for business users, the change in interface design instantly reduces productivity and buy into the tool.

* Add relation for workload estimation between stories and subtasks * Linking to Confluence could be implemented. At the moment links can only be created from Confluence to JIRA, not the other way round.

Better ability to add numbers in ad hoc queries and search results, e.g., total development cost estimates.

The reports and dashboards do not provide for reports in a graphical way. The tickets cannot be simultaneously assigned to two or more users.

Tree view of linked issues.

The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable.

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 but, JIRA support responded immediately. Within a couple of hours, the problem was resolved.

* It should be able to open a channel with a customer through chat or remote desktop. * It should be able to define my KB articles and link it with a self-service ticket.

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. You can do a lot with the tool but again, but it is not a 100 percent solution for everything. We have a lot of acceptance criteria coming through it, but JIRA doesn't support it. Therefore, we have go to different user stories and break them down.

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. Right now, if I attach something, it will go into a single attachment pool for the task, not at the comment level. I.e., If I want to attach the new version of a document, it creates confusion because I have to remove the existing attachment. When writing comments, there are not many options for formatting. We were expecting formatting something at the level of Microsoft Outlook or Microsoft Document. When creating a task, there is no place to add our estimation.

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. So, you have to use some add-ons and create a lot effort to obtain information from the tool. Thus, you have to adapt to the lack of search that the tool does not offer.

* Report customisation could be improved. * Out-of-the-box reporting is limited. It would be helpful if more customisation was possible.

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.

The reporting and the view, from a story to a defect, should be improved in the next releases. For example, how many boxes are assigned to one story, or how many tests are run on one story, and so on. This is what I miss in the tool at the moment.

I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, in a good way. 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. For instance, if I rate an Epic, the Story points, and I rate the related user Stories, the Story points, they all count together. They're all summed up together. So, the overall Story points for the Epic, including the Stories, is double of the Story points. It just doesn't make sense. Maybe I'm doing something wrong, but I had to delete all my Story points on the Epics because they were counted including the Story points. This is not correct, and I would immediately improve that. 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.

It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins.

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 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.

As a Technical Writer, I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA.

Right now, the Task Management feature and Confluence are separate from JIRA itself. So, we have this problem where sometimes these modules don't talk to each other the way we expect them. So many times, links created automatically from new tools apart from another tool which didn't work, therefore you have to manually go into the task, even though the link is right there. Another example, in JIRA you create a test sessions with user stories, then buttons from the user stories can automatically change the status of a test session from started, completed, or paused, which doesn't work. Therefore, there is a problem there: inter-module conversations.

When creating Epic, Story, and Task, there is no provision to set estimated time. The estimated time can only be set once the ticket is created.

The following definitely need improvement: * UI * Speed * Mobile app functionality.