JIRA Room for Improvement

Alexander Dobry
Fachbereichsleiter with 10,001+ employees
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. View full review »
Chigozie Okereke
Senior Quality Assurance at Pegb Technology
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. View full review »
Anaya Struncova
Software Developer at a tech vendor with 201-500 employees
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. View full review »
Find out what your peers are saying about Atlassian, Microsoft, Micro Focus and others in Application Lifecycle Management (ALM) Suites. Updated: October 2019.
372,906 professionals have used our research since 2012.
Jonathan Machado
Senior Test Engineer at a venture capital & private equity firm with 10,001+ employees
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. View full review »
R&D manager at a engineering company with 10,001+ employees
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. View full review »
Andrey Agranov
Java Development Team Leader at Honeywell
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. View full review »
QA Automation at a tech vendor with 501-1,000 employees
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 »
Walter Ebeling
Senior Vice President Global IT Services at a logistics company with 10,001+ employees
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. View full review »
IT Developer at a financial services firm with 10,001+ employees
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. View full review »
Pre-Sales Consultant at a tech services company with 10,001+ employees
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. View full review »
Neetu Singh
Engineer -QA at a financial services firm with 10,001+ employees
The reports and dashboards do not provide for reports in a graphical way. The tickets cannot be simultaneously assigned to two or more users. View full review »
Gianni Rigoni
Digital Engagement Manager with 10,001+ employees
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. View full review »
Satyajit Roy
UX Architect at a software R&D company with 51-200 employees
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. View full review »
Senior IT Test Manager at a financial services firm with 10,001+ employees
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. View full review »
Ananthi Nachimuthu
Senior Technical Writer at a software R&D company with 201-500 employees
The user interface and views on different devices should be improved. The customization feature can also be improved. View full review »
Scott Warnick
Integration Engineer at a tech services company with 10,001+ employees
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. View full review »
Kijal Parekh
Digital Test Lead at a comms service provider with 1-10 employees
The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable. View full review »
Aleksandra Smarovidlo
Technical Writer at a tech vendor with 11-50 employees
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. View full review »
Peder Herborg
Head of Strategic Development, Retail with 201-500 employees
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) View full review »
Sami Abu Shawarib
Senior Implementation Manager at a tech services company with 501-1,000 employees
* 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. View full review »
Daryn Louw
Head of Product with 51-200 employees
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. View full review »
Sr. QA Manager with 501-1,000 employees
It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins. View full review »
Kevin Doyle
Business Analyst, Scrum Master & Agile Coach at a tech services company with 10,001+ employees
* Report customisation could be improved. * Out-of-the-box reporting is limited. It would be helpful if more customisation was possible. View full review »
Arun Srivastav
CEO with 11-50 employees
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. View full review »
Rolf Schweingruber
Head of Embedded Development with 11-50 employees
* 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. View full review »
Jean-Marc Iribe
PMO manager at a manufacturing company with 10,001+ employees
The hierarchy for Jira tickets is too flat. View full review »
Scott Moshier
VP - Data Solutions with 11-50 employees
The permissions can be challenging to get right. View full review »
Dan Carnahan
Service Owner with 501-1,000 employees
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. View full review »
John Sell
Regional Vice President with 51-200 employees
Better ability to add numbers in ad hoc queries and search results, e.g., total development cost estimates. View full review »
Louise Fozard
Head Of Portfolio Management with 51-200 employees
The reporting needs to be improved. View full review »
Baskaran Senthivel
RTE (Release Train Engineer with 10,001+ employees
Tree view of linked issues. View full review »
Manager, Live Production at a software R&D company with 1,001-5,000 employees
The following definitely need improvement: * UI * Speed * Mobile app functionality. View full review »
Find out what your peers are saying about Atlassian, Microsoft, Micro Focus and others in Application Lifecycle Management (ALM) Suites. Updated: October 2019.
372,906 professionals have used our research since 2012.
Sign Up with Email