What needs improvement with Jira?

We haven't seen Jira's progressive area so far, and we are not sure what it might do in the future. Due to Jira's access controls and role-based functionalities, we have some limitations, limiting our full exploration of its capabilities.

The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement.

The solution could be cheaper.

At times, I am not able to report a bug. Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required.

Improvements in Jira for the next release could include adding AI tools for dashboarding, making it easier to report insights, and enhancing business intelligence capabilities. It should also improve on-prem support. As far as I know, Jira's on-premise support is being discontinued. From last year onward, they stopped providing on-premise licenses and now only offer cloud support. This shift happened gradually, and I believe they now only offer cloud licenses.

There could be an improvement in loading files and images for more than 50 MB. It would be good if it allowed more than 100 MB. Additionally, Jira analytics needs further development to analyze code, but we should keep the queries. This will allow us to delve into the details of completed tasks, work in progress, and pending items. However, more information regarding graphical representation is still required. Considering the number of test cases, it's crucial to have comprehensive data on completion status, logs, and retesting. Jira excels in providing such detailed information.

In project communication, it is necessary to train every new member who joins us for Jira. Apart from training, using Jira for project planning and scheduling can be very helpful. Remote collaboration is helpful. We need to conduct screen sharing sessions with everyone, it would be even better if Jira could provide integrated screen sharing capabilities and enhanced email communication features. Therefore, the release of a MailServer feature within Jira would be beneficial. If I want to create a Jira account, I need an email ID. If Jira will provide the same functionality as Gmail, such as a mail server, then collaborating via Jira email will be possible. Additionally, for trained individuals, we can share screens within Jira itself.

ClickUp is a good alternative to Jira, so they have a better interface [GUI]. I don't like Jira's graphical interface - it could be more user-friendly. Jira looks old school. Also, the administration part of Jira should be simpler for project managers and Jira administrators. It has many configuration areas, which can be confusing. So, the administration part could be more simplified.

A lot of companies use a mix of Waterfall and Agile methodologies. They often need more individual metrics for time and cost tracking. Many larger companies would like to have more resource management within Jira. The model for adding features is by application. If we add an application to Jira, we must pay for the licenses for everybody on our contract when only a few people need to use the application. Adding applications is very expensive. We cannot make it for only the few users that need it. We must buy the application for the entire workforce that's using Jira, so it's not very flexible.

I want the tool to integrate connectors.

Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects. The high level of customization and feature-rich nature of Jira are confusing for new users, requiring some time to learn and navigate. Administering Jira, especially in large organizations with complex workflows, can be challenging and may require expertise.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

There are a lot of things. A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product.

Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc. The history of tasks, such as check-in and checkout, is not maintained under the particular Jira ticket. For example, in Azure DevOps management for a work item you can find out any chain set and dependency.

The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified. I don't have any requirements for new features. It is a standard system, and we use just a part of the functionality.

I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues, epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand. When you want to create something in Jira, whether it's a story or an epic on a task, you have to create a thing called an issue, and inside the issue, you have to put what type of issue it is. Either it's an epic or a story. The fact that it's called an "issue" was a little confusing for me because I didn't know where to search when I wanted to look for tasks and stories. I didn't know that I needed to search for issues and not only tasks or topics.

Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate. Jira should understand that at the leadership level in an organization, such as the C-level or even below that, they don't like to have an epic creator. Rather, they are interested in observing all of the corporate objectives that are being turned out by the team. OKR is a very important feature for them to add, and it's a big investment. There are separate tools that are trying to support and enable people to use this framework. If Jira could do that, it would be great because we don't want to integrate multiple tools. For example, we don't want to use one for OKR and another one for Agile backlog items. If we can have support for everything using one tool, it would be helpful. That said, it would require a big investment to implement. The biggest drawback that Jira has is that they don't have a separate chart to show metrics for lead time, cycle time, and throughput. We use the control chart as a workaround but it's not giving us the correct metrics. The metrics are skewed because the chart shows us some items that are still in an open state. This is something that needs to be fixed. By comparison, Rally Software has a feature that enables people to understand the lead time, cycle time, and throughput as separate metrics in different charts. Having Jira implement that capability would be helpful. We are unable to enter an explicit agreement below the kanban board, which is something that we would like to be able to do.

Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira.

The integration could be better in Jira.

Reporting is something Jira could work on. The reporting capabilities should have the same flexibility we see in Excel, including the ability to manipulate data and create graphs. They need to have that, so we don't need to export to a spreadsheet. Jira should add some features from another Atlassian product called Confluence, which we use to track all the documents we need for development and testing. There should be better integration between Confluence and Jira. I like to use Confluence to do my reporting, and I should be able to go into Confluence and launch reporting at the source. Jira acts as a data source, and Confluence is where the dashboards are. It would be easy for Atlassian to develop all the dashboarding capabilities for executives so they don't need to log into Jira. There's too much there. It would be better if executives could log into Confluence, which is a document-based tool.

The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes. The out-of-the-box version of Jira has minimal to no testing functionality. I have to use Zephyr to be able to track testing. The time logging is also not easy to use, or user-friendly. In the next release of Jira, there should be test cases in the test reports. Better burndown and burnup reports should be enhanced. Additionally, the usability of time logging could be better.

Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects.

Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability. It depends on your usage pattern because if it's more configurable, you can configure it to be a very different kind of tool which is a benefit.

Jira's collaboration and integration with other apps and tools could be improved. Jira does not focus on ITSM documentation and procedures. It is more advanced in user-friendly workflows but is missing the functionality of artificial intelligence AI which could be embedded in the ASM management.

The solution can improve by including test management functionality in a native bundle without plugins.

There should be a way to look for specific comments. When we have thousands of comments in a Jira ticket, there is no way to look at the comments of a specific type. In the comments, if there is a way to put a tag, it would be helpful. For example, when there are a lot of lengthy discussions happening on a particular ticket, there could be a conclusion tag or something like that to indicate a conclusion. It would help in sorting the comments based on a certain category, such as conclusion. I should be able to tag a comment with something like ##dev_conclusion##, and someone looking at the comments should be able to expand all the comments and search based on this tag. Some of our tickets can go up to 100 or 200 comments, and it currently takes a lot of effort for someone to go through them. It would be good if there was a way to preview the comments. We want Jira to be the single tool that people use. We lose a lot of information when working at the ticket level in Jira. We don't want to have discussions in Confluence and design docs somewhere else. Currently, we make some decisions outside, and we make some decisions in Jira, and there is no combined way. There should be a way to integrate documentation into this, and I should be able to directly update the documents. They can also incorporate a review mechanism for documentation. I should be able to assign a sub-comment to someone to say, "I'll respond to it," or I should be able to tag someone to say, "Can you please look at it?" We should be able to use a workflow. There should be some built-in intelligence where when there is a design document in a Jira ticket, the signoff should be done by certain people. Currently, the documentation is completely separate. If there is a way to get the documentation into this whole workflow, it would be useful.

We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product. In general, however, as a solution, it's quite complete and I cannot speak to any missing features.

Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see.

The solution could be more user-friendly.

Jira could improve the documents management level. Our customers compare it to Office 365 and Sharepoint Online. They are focused on versioning of the document; Jira is missing this in their environment. It is missing functions for collaboration, like instant messaging. Currently, we try to connect the systems, we use Jira workflow which is connected to Office 365. Jira is trying to push for the online version, however, our customers are not ready to do that due to safety concerns. The features are not intuitive. It would be good if there were templates.

Jira has a lack of graphical interface that maps the different cases to the space or in the project. For example, if you have a project that has a big diagram of component systems, people, and use cases, each of those Jira cases usually can be mapped to a specific location. This can be enhanced by a curve set of Jira, or a curve set of screens, where you can map on which pieces of the project you were working on at that particular screen. When working on the left side of the diagram, or the right side of the diagram, you should be able to request all those Jira that are related to that part of the project. If a system has ten different steps of data flow and the components are clear. You should be able to map those Jira cases to different steps in the process. This would show you how a field or component is related to a location in the diagram. The diagram then would show all the cases waiting to be done or already done. Jira works too slow, especially when you are in a big organization with thousands of users. It is also too slow when integrating with other components like SVN or with a built system. I would like to see everything that Jira does is under have a second response time.

Sometimes, the status change is too difficult. The change of status is not configured correctly. We sometimes have a limitation on the number of changes that each workflow can do, so we get very restricted with the changes, and status change gets difficult. It could be specific to our implementation. Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done. Color codes are currently missing in Jira. It is very limited in that aspect. I would like to be able to color certain impediments or features in red. I don't want to look at everything ticket by ticket. I just want to be able to look at the colors and see where we are. I am not getting that in Jira currently. Maybe it is there, and I don't know about it.

This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning.

Sometimes it takes time to load the data.

Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly. For admin to get permissions and stuff like that for their members it's a little confusing sometimes. That said, the rest is very clear. The integration of what we call "Issues" in Jira could be better. The Issues integration with Bitbucket Pipelines could be better. If Jira can provide an easier way to configure and use this functionality, that will be helpful for workers.

Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure.

If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side. Another enhancement could be in the area of interfacing with other products or connectivity. It could have better integration with other tools.

The only complaint I have about Jira is that there is no field-level permission for the issues in the Jira cloud version. You can get an app for the server version, but the cloud version doesn't allow that type of functionality. For example, I write a user story that goes to the customer for approval. Once approved, I would want to be able to lock the description for that user story so it can't be changed, but I'm unable to do that. I can lock the whole story but not the description alone. It creates a problem because when I need to add the story to a sprint, I need to change the sprint number field. It can't be done because the whole issue is locked or lacks the properties to be edited. The other thing missing is a straight connection to the pipelines and the source control. I think it should be integrated with GitHub and other products that developers use. It's the lack of integration that's the main reason we are considering moving to Azure DevOps.

The only thing in our current setup that is a bit difficult is that Jira is a bit of a black box. Only we see it, our customers do not. I know that we can change it but we have not done the work to do it. Jira is not compatible with our current Microsoft infrastructure. We are using SharePoint along with WorkPoint in our environment, which is used for document management and process management. For projects, it is a better connection between HelpDesk and the projects. Moving into SharePoint would help. If Jira would be interested in offering a SharePoint version, it would be beneficial.

If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications. It should have more Trello-like features. There are some things you can do in Trello, but you can't do them in Jira, which doesn't make any sense because Jira bought Trello.

The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit. When using the service desk and the developer, the transition could be better between the two. For example, we asked the support desk to send a ticket over to the development and it was a little bit cumbersome. We had to recreate another ticket for development, then we had two tickets, one service desk, and one development. It would be beneficial if the process was more smooth between those two packages.

The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me. Understanding the workflows can be a little bit difficult. For example, if you don't know the workflow well and you get an error, which is not a technical error, you won't be able to find the reason for that error.

What I don't like is that perhaps there are not so many different apps that can add value over the management side of the product. They're not able to develop over Jira, even for normal technical activity signing. For managing the project better or for task documentation or even managing tickets or service needs in another way, there needs to be better customization or better apps. I'm really obsessed with the idea of reducing the number of activities to have a general retail workplace. However, if we need to expand the use of the Atlassian suite to all the teams, all the people, we need something that can be, easier to use and has the ability to offer more guidance to those users that usually don't work with these type of tools. For example, ServiceNow doesn't fit all the needs in the company, however, it can be configured. You can develop so many different functions over it. I don't want to increase the payments and the number of licenses that I have to buy from ServiceNow. I would prefer to have my own developed team and try to define everything on our side - including the functionalities that I would like to build for those proposed functionalities.

Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas. Nowadays, you see a lot of product management tools, like monday.com and they are very user-friendly. They offer features that allow for cosmetic changes, and you can actually change the color and the form to your own liking. ira is lacking some of that flexibility. It's not critical, however, for the wider user base, many would like to see that.

The solution is not as intuitive as it should be and you have to play around with the environment quite a bit before you get a handle on how things work. One of the issues is that it's usual for a ticket to have a primary developer on it and other people supporting, but that's not possible in Jira. They have a very thick policy and a ticket can only have one assigning, although it may be possible to do it as a number coding, I'm not sure. I'd like to see the solution include a feature whereby you can link stories visually, to explicitly show the connection between a user story and a task.

As the solution is highly configurable, it has very poor governance. There is nothing which comes out of Jira to go into the product. It is free for all and anyone can create with it. This means that the responsibility lies with the user community to create some form of governance. Moreover, the solution is geared to small teams. It lacks scalability. The tool is not good at the enterprise level. This means that, depending on how the person installed the software, the issue of performance may increase commensurate with the number of projects. While plugin for x-ray exists, it is not that mature in test management. Although it's a good tool for many of the smaller clients, once a person goes deeper into it, it's not there, even though it will get the work done. It is a less desirable solution in controlled environments, such as science, banking and finance, in which there is a need for certain compliance supports. The solution is not that great for audit histories. It's a great tool when much integration is involved. With cold products, things can always be achieved through other means. When the teams collaborate, they need multiple metrics to be tracked. With this comes the issue of direct impacts, such as the appearance of one's UI and its usability aspects. The screens have changed greatly in appearance over the last ten years. This is an issue which every software dealt with in line with the growth of usage and complexity.

I would like to have a future-proof idea of the cost and the roadmap for my class. This is in light of the fact that they are switching things up, promoting the cloud service and mixing different support levels. The CMDB and knowledge platforms that are in the background of the ticketing tool should also be addressed.

One of the issues is tracking the hours that people spend on each task. I know the solution has some built-in features but it doesn't quite meet our needs. We tried a couple of expansions unsuccessfully. Being able to track the effort on each of the tasks is important for us and we'd also like to be able to compare that with what's been budgeted. It would be useful. We've recently moved to Teams and some of the integration with Teams doesn't seem to work, whether it's not supported or not there, the ability to integrate that would be something we'd like to see.

One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better. Another thing that I don't like about it is related to epics. There are times when you simultaneously want to have a story tied to two epics, one driving the content change and one driving the format of that evolution. It is not truly a parent-child relationship. It is a single-parent relationship to the stories. It would be nice if you had the capability to tie in multiple epics to a particular story. It is a rare case, but we have that. Setting up and executing a triage board should be simpler in the sense of how you do the admin. I come from a regulated space, and there should be easier control of who approves and reviews a system board to oversee all the defects. It should have easier out-of-the-box solutions to allow us to set up a triage board at the system level, at the software board level that reports to the system board, or at the test level that reports to the software board at the system level. There should be out-of-the-box solutions to migrate that and say that who are the three people on the triage board and if they have these admin privileges. Software review board and test review board would be another thing. We have also had a problem with the integration with Bitbucket Pull Request data. It is an add-on to the tool, but it is not fully integrated. It is not easy from my perspective. Jira, Bitbucket, and Xray should be smoothly integrated. Xray is pretty good, but Bitbucket is standalone. So, when you pull out the data from a comma-separated value and want to move it into a new database, you have to reenter the data. You somehow lose that Pull Request capability. Pull Request through Bitbucket and the review of the code should be easier to manage. You could use a software package called Crucible to go ahead and mark how you did the review, who reviewed it, and who is the independent reviewer or subject matter expert, but that also should be easier to set up. If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool. I'm using Jira for the requirement repository. When I do requirements, it would be nice if I had the capability to say that for your requirement, I'm going to give you traceability to support a traceability report from Xray. I'm also going to give a requirement ID number in the ticket. You could use Jama and things like that, but it would be nice if Jira supported that. We had on-prem and cloud deployments. We had to go to on-prem because of the security measures that were deployed. On-cloud didn't have the same capability. If you have one database on the cloud and the other one is on-prem, they don't talk to each other. It would be nice if you pulled it in and you could switch and say that I want to go on-prem because I got greater security risk. When we go into the regulated space, I require a lot more integration and capability for tools. It is very hard to get tools to perform at that level because they're built for the general audience. In the regulated space, whether you're in medical devices, avionics, or any other regulated environment, tools have to be validated. I've worked with some companies in the past that had the capability to facilitate that validation. With one of the solutions, you could go ahead and buy a validated suite or a requirement package that will validate the tool for your use, but it is such a small market for Jira around the world that nobody really cares about that. On their website, they show a bunch of tools that work with Jira, but it would be nice if they gave you examples and said that if you're a regulated medical device or regulated, here's a solution that could work for you. Here is Jira. Here is Crucible, and here is Xray, and here is what it'll do for you. They could also ask how do you do the requirement management? Do you use Jama that ties to Jira? It would be awesome if they had some use cases that showed people how to use Jira as the building block and how to add something on the front end for requirement management, and something on the backend for testing, such as Crucible for the peer reviews and Xray for the test management. People would see it and say that I want to do that. It would also be nice if it could provide some lock-out capabilities based on your development and environment preferences. For example, you can specify that no one can close a defect until it has been tested, or until a particular task is complete, you can't go to the next phase. It would be cool if you could have something like this set up versus someone configuring it in the background.

The performance could be improved in the future.

The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly.

They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that.

The transfer of the functionality between testing or pre-production and the production environment could be improved. It would be helpful to have more automation in this area.

The solution, in general, is a poorly designed and confusing product. The user experience is not ideal and the user interface is convoluted. The interface in particular could use a big refresh as the actual navigation within the interface is not particularly smooth. The work items structure is not hierarchical and that needs to be changed. It's too flat. There's excessive scope for customizing the project and the platform. Therefore, there are too many integrations, which leads to very high levels of complexity in terms of management. Key indicators that are useful to Agile teams such as burn-down charts or burn-up charts, cumulative flow control, et cetera, are available, however, they're not easily accessible from the default user view, whereas they should always be present. Key indicators must always be present. They actually take a couple of clicks to actually get to them.

The UX and UI could be better. It's something they need to improve upon. It needs to be updated and made more modern. It would be ideal if the solution could be available as a mobile application. We would like the solution to be a little less costly, although, overall, the price isn't bad.

The user interface could be much better, although it's good enough to do the job. I don't see the mobile application for this particular application. I use it on PC. I tried to download the application, but there are some constraints to using it. It doesn't link properly, it doesn't detect my Jira board, even when I have entered the name. I don't know how to use that app. I download and tried, but there is confusion. There is no clarity on how I can map my desktop account with the mobile application. There is definitely room there to improve. There should be a way to integrate the mobile application or in some way, make it more clear because at first instance, I didn't understand how to use it.

The Defect section could be improved. When you're trying to keep track of the requirements and the Defect section, this setup could be done better. I was struggling to set it up. I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira.

I think that for users the solution is very intuitive but for project administrators, the way the product is defined is not very intuitive. There are too many ways to do the same thing. The setup of Jira sometimes becomes very, very cumbersome and difficult. It's not very easy for people on the project admins to really understand how to set up the product because of these features. If they were better organized and the documentation improved so that people would actually be able to figure out how to use Jira, that would be helpful. There are not many videos and it can be very challenging for anybody not familiar with the product. There are 50 users on the project I'm working on.

In terms of what could be improved, it is a bit harder for management or the business partners. I used to search the Atlassian Community online for some troubleshooting issues and I think there were some issues that seemed to not be a big problem for other similar applications, like Microsoft Teams, that were not considered by Jira. So I hope those will be considered soon. I think for some, the help documentation has been hard to track, so that I had a bit of difficulty finding the solutions. I'm the end user. I'm not the problem solver.

In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful. When I first started using Jira and we were in the middle of coming up with a solution, I found that there could be better separation of tasks when it comes to user stories and epics. For example, right now we can take users and sub-task them, but the developer is not able to easily ask for or request a task as a separate thing to work on. Other than that, I would definitely appreciate more kinds of features in general. But we have already requested these from Jira ourselves with their voting system. These requests are in their backlog now and we hope to see them in future soon.

There could be some improvements in the project management and portfolio level features. I think they could bring more flavours of Agile to Jira, that would help.

We're more focused on other solutions. Jira could be more, for example, like Micro Focus, which is what I mostly work with currently.

Stability is an area of concern and it needs improvement, otherwise, it's a good product. In the next release, it should be more stable and have more APIs to integrate more plugins with it.

Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature. Because right now, we're using third-party tools to test executions. If there are multiple projects, it could be a good thing if they had a reporting method where you have a portfolio view with predictions and so on. If there were a way to manage all the SLAs, that would be helpful too.

I'd like some more features around software testing. I'd like to see some more stuff done around data testing. That's what I'm most interested in. They could be better around generating documentation and essentially helping with test scenarios, test cases, or test results in a way that is more user-friendly. The product needs to be more flexible to adapt more effectively. Sometimes you fix the style or the format and it might not suit the environment. I'd like to be able to more effectively configure it.

The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything. While it should be a standard thing across the company to have labels created in certain way, the system should be able to pull up suggestions of labels that are close. The product could be more intuitive. If something isn't getting resolved, we generally aren't getting any alerts to warn us to this fact. We don't get any visibility on if something's been open for a few months even if it should have been closed after a few days. We need some sort of system that shows us items that are lagging.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

Produce improvements suggestions: User Interface/ User experience could be improved by expanding on visual capabilities of links such as Stories, Requirements, Scenarios, Cases, & Defects. User Dashboards could be improved by increasing ease of use of charts and other interactive options such as Boards.

The GUI should have much better features like more graphical illustrations. There are some cases or benchmark data that we are trying to capture and customised into a graphical pie chart summary dashboard, but unfortunately JIRA is not able to do that.

The user interface is very detailed right now. It could be simplified if they consider targeting the user experience. Right now, on the screen pre-design, the amount of information on the screen is very high. The distribution is good, however, the presentation itself looks very technical. They should work to streamline the UI to make it better for users to digest the information.

When a task is completed, it disappears and I don't know how to find it. If I want to go back in history to review an old task that we completed, I cannot find it. Unless you remember a keyword or a task number, it can be very difficult to find old tasks. Sometimes, in the display, there is an overload of information that makes it very difficult to read. If there's too much information, it defeats the purpose. You have to reach a balance, and I think at the moment, there can be too much information. Sometimes the interface is too crowded. It seems like the default option when you open a task is that everything is open and all of the menus are deployed. There needs to be easier integration with third-parties — personally, this is the biggest issue for me.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews. It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories. In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

The filtration could be better.

Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed. It's my understanding that the reason they started doing the Next-Gen and changing up the whole dual-end functionality is probably because of how heavy and big everything was getting. It had gotten pretty complex within the Classical Projects. It's quite time-consuming picking up the Classical Projects. They've gotten quite heavy and it's hard to use them in a productive way. There are just so many settings and possibilities. It's very complex and time-consuming, however, on the other hand, it's got everything you need in terms of functionality.

The sprint-related graphics need to be improved. They are using story points for the sprint breakdown graphics. When you have five large stories with several story points, in the first week of the sprint, nothing gets done. This means that you have a flat line and then, in the end, all of the stories are done at the same time. So, we created all of the graphics but they were useless because it was just a horizontal line and then at the end of the sprint it dropped down to zero points. Basically, it was a square. In the next release, I would like to see a good graph that takes into count what you put into your stories.

There's always room for improvement, however, it depends on how you intend to use the solution. It's hard to pinpoint exact features that are lacking as the solution is quite vast. From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example.

There's a bit of a learning curve, which I'm not a huge fan of. It's not exactly user-friendly per se. I would prefer it if the solution was more intuitive. There are just so many options, that it's pretty overwhelming as a product. There's too much to focus on. We do find that we need plugins and have created integrations with more robust analytic solutions than Jira provides. Personally, I'd like it if there was more flexibility in how you could manage the backlog at a project level.

The performance is not so good sometimes. I know that fully depends on the implementation and the IT environment of Jira or the version of Jira installed. The performance is sometimes not so good. I would like to have a better response time from the Jira server. And it fully depends on the administration side of the Jira.

A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time. So I have to do multiple exports to just create the sub-tasks and sub-tasks are not being reported. If I wanted to export this and recreate this in another platform like Azure DevOps, I would have a problem right now.

The help desk and services management features are in need of improvement.

The solution needs performance improvements. We see that a lot of times it's clocking whenever there's any abuse. When we switch from one view to the other, it takes some time before that view is presented. The performance for different dashboards, whenever they are loaded, it takes more time than you're comfortable with. Whenever you move from one dashboard view to another dashboard view, then it should come up quickly. Right now it takes a long time and sometimes it clocks. The overall product performance, whenever you switch a view is what they need to work on. Whenever you edit a story, whatever you have changed takes a bit of time to save. The integration between Jira and Jira Align needs to be better. There's a lot of differences between the two systems. I believe what happened was Jira bought this software from a different company called AgileCraft. And that integration is still in process, and, because of that, there's a lot of differences between the statuses. That sometimes creates a lot of confusion for senior management whenever they're reviewing performance across teams. Better integration between Jira and Jira Align is on the top of my "most desired upgrades" list. The solution should improve performance when there are multiple users.

I would like to see more robust release management within the tool. We're not able to use it at this time because of compliance issues within our industry. At this point, I'm not confident that it can meet the requirements.

it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do. In the next release, I would like to see better integration with other software. Many companies have a lot of peripheral systems. They have ServiceNow or they could have something else. How do they integrate your stories, your sprints, or if you have confluence, or SharePoint when you start using Jira? The challenge is when you have someone who is not using confluence, but they have SharePoint or ServiceNow. How do we connect, or integrate our stories with Jira, so we don't have to have the information in three different places? The integration and integration threads would help Jira going forward.

In terms of what could be improved, there is not much I don't like. It is a little bit faster but with Firefox it can be slow, but that is also the case with many other tools as well. It has quite a lot of options and fields, so I'm not too familiar with them all. That makes it a bit trickier. It could be a little bit easier, it is not that simple or straightforward. The tool itself is so powerful and the customer's expectation is very high because you have so many things you can do with it. That can make it a little non-user friendly. I would want to see Jira include some improvements, like drag and drop and color, to make it more straightforward. If you compare it to Microsoft or Octane, they have good features that I would like to see in Jira as well. Overall, Jira is a little bit old fashioned, it could be more user friendly. They should make it simpler, to just be able to do some functions, whereas now it takes longer. There are too many clicks.

I have been watching an issue develop. There is a difference between their cloud and their server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it. Additionally, it would be really nice if they added some custom reports so that you could build your own report through any open source or commercial plug-in like Crystal Reports. That would be much easier for them to accelerate. You can create a report template and use it frequently. There are a few features I would like to see in the next release. For example, the layouts could be easier to configure on the screens. I know it's easy to customize. For each issue type you can create and modify your screen. But it would be easier if you could enlarge, copy, clone, and visualize them in a model in a visual way. It's really hard for me as an admin to compare different screens or even to copy one screen with one additional field. I believe that is creating a lot of confusion for end-users because usually admins are looking at each field independently, where it's located, in which position, and which screen. So that all needs to be improved from an administration point of view to make it easier to visualize and compare between the screens.

I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. There shouldn't be the need to go through this. The process should be improved. It's not so good for testing.

The team construct could be simplified. We use Jira with Tempo Planner, and Portfolio for Jira, and at times it is not always clear. With Portfolio, it's the same as Jira but with Tempo, it clashes. It's not a seamless transaction. We would like to see integration between Tempo and Jira. For example, if I create a team in Tempo, I would like to be able to use it and re-use it Jira as well. In Tempo, if you create a team then you are able to link that to a project in Jira. I would like to have that same capability, where I can link to Portfolio for Jira. Specifically, if I create a team in Tempo then I want it available in Portfolio. When I am planning the work for my team, it would be easier to have that capability available.

In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities. There needs to be more training modules and more emphasis from the company on proper training and product overviews so that users really understand its capabilities and can actually use the solution effectively.

The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways. A lot of the user interface could be updated. Technical support is lackluster. It could be improved. They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.

The integration and management features need to be improved. When you first start to use the interface, it is confusing.

Jira has recently updated their UI, but more can be done to make it even better. One thing that is missing is notifications that we can send out in an automated fashion so that we don't have to log into Jira every single time. We do have dashboards on our navigation pages, but we need to log in to see the current status. I can't just click reports every once in a while to trace or track projects, I have to log in to see. I'd prefer it if the data automatically came to me instead of having to go seek it out. It's possible the dashboards and the reports are something that can be properly configured on our end. However, I'm not the Jira administrator in our company. I probably just don't know how to do it. Jira may actually be able to trigger these kinds of reports. However, if they don't have this functionality, it should definitely be added.

It's a pain getting it on the public, it costs too much. It's also difficult to migrate through, things don't always tie-up. It's not easy to use and it's not as intuitive as it should be. I stay away from it as much as possible.

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.

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.