Jira Room for Improvement
The way that Azure DevOps rolled out their boards and made them flexible is something that Jira lacks. You want a workflow and you're configuring your columns and you're mapping status to columns, however, in Jira, you can't have more columns than you do status. Whereas in Azure DevOps from a Jira admin perspective, it's amazing as it doesn't care what you need in terms of what your life cycle is. The underlying process template is very generic. It's just like a to-do, in progress, done ordering basically, except they use the words inprog or active, resolved, and a couple of others. Open, active, resolved, and maybe one more.
No matter what they do to the face of the board, they can create 15 columns if that's what they want to represent their lifecycle, which gives them that visibility and the ability to then report on that. The reports will run off of that, however, they never have to actually reach out to an admin and say, "I need you to build me a workflow." On the admin side of Azure DevOps, they could modify the underlying process template to include things like that would be the equivalent. They refer to them as rules in Azure DevOps, however, it would be the equivalent of post functions and validators and these things within Jira.
The great majority of teams don't care about that. What they care about is just being able to properly represent their lifecycle. It provides a great deal of flexibility and it cuts down a tremendous amount on admin having to build a workflow for each and every team that feels that their process is somehow different than everybody else's. It lets them basically self-organize. Agility, being able to just boom, build out their workflow as they see fit. That's the biggest thing that I've seen so far that Jira could really learn from.
In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting. Now the issues themselves, of course, the activity, the history, all of it is still there, but you lose all your boards. Not the boards per se, but the reporting within them. That includes all of my past sprint burndowns, all my past velocity reports, some of that stuff gets completely wiped away. The only way to restore it is to replace the original workflow. It's insane. It's the way that the application is built and it's all tied in with it. I had it explained to me one time by Atlassian, however, it's just really a bad thing - especially when you're in a large enterprise organization and then you get somebody like me that comes around that they hire to come in and be the product manager. The first thing I say is, "We need some fricking governance. You can't have 100 plus statuses. What the hell is this? Or 500 custom fields that half the people aren't even using."
The statuses in the workflow standardization become virtually impossible as I can say, "Hey. This workflow that you're using is a terrible workflow. Let me fix it for you. Let me give you a better workflow. Let's talk about this. Let's build a really good workflow." We need to go through that pain and then I have to tell them that, "Oh, and by the way though, if you adopt this new workflow that I'm sitting here telling you it's going to be so much better, be advised that you're going to lose all your reporting history." How do you think that's going to go? Probably not so good. That is a huge downfall.
Senior PM / Scrum Master at a financial services firm with 1,001-5,000 employees
One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. In Issue Navigator view, Jira allows you to enter JQL, which is basically like SQL. You just enter a query, and it displays the stories that satisfy the query. There is a field called Epic Link, which is basically a high-level designation for a bunch of user stories with a common goal. Epic Link is typically of different colors. When Epic Link's background color is a dark color, it effectively becomes unreadable. I am looking at my screen right now, and there is an Epic Link called Click View User Request. The background is purple, and the text is black. It is almost impossible to read it unless you click on it or give it an extra minute of viewing. That's basically what needs improvement. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view.
I've been required to report on metrics, and I don't know if it is possible with Jira, but there needs to be an easier way to capture a few metrics. For a two-week sprint, we are required to report on a number of metrics such as committed, completed, added, and rolled over. There is a way to see the stories that have been added after the sprint has begun, but there is no easy way to aggregate this, which is a waste of time. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell.
In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it. There should be an automatic aggregation of how many story points were added after the sprint began and how many story points were rolled over to the subsequent sprint.
I also wish Jira had an indicator to tell you that you are approaching the limit for the story points that can be delivered during a sprint. Typically, there is an established capacity for each sprint. I take an average of all of the delivered story points from the past six sprints, and I use that number to estimate how many story points can the squad deliver. I wish there was an indicator in Jira that tells you that you are approaching the number of story points that can be delivered during the sprint. I don't think there is an indicator like that, but such an indicator will be very helpful because then I will be easily able to see that we are approaching the limit. I can then talk to the squad members and say, "Okay, we need to remove some story points from the sprint because we're reaching capacity."View full review »
For how I identify tasks and break down use cases, I wish there was the ability to drill down Stories multiple levels deep. You have Epics, Stories, Tasks and Sub-tasks. Each of which can go one level deep. It would be nice to be able to be able to define Stories multiple levels deep in order to break down super complex use-cases. That is my only pet peeve. Other than that, they've been improving year to year, and each new version seems to have increased levels of improvement.
I use another product that synchronizes well with Jira called Worklog Assistant, by Sohail Somani, which runs separately to Jira. It is a great product that allows you easily keep track of work performed and generate all respective Jira worklogs at the press of a button. I've been using it for years, and it just makes it very easy for me to keep track of what I am doing with an accurate time tracking mechanism. I think this would be a nice tool to integrated with Atlassian Jira.
Product Engineering & Operations Director at a tech services company with 10,001+ employees
There are a few things about it that I think need to be improved in terms of the ability to build reports. We would like to be able to use the data from Jira to help drive Gantt chart roadmap-type views of not only what we're building, but rather where we're going.
What we've elected to do in a couple of cases is just pull the data out of Jira and then pull it into Power BI so that we can try to get some of the more sophisticated information that we want out of it. We actually experimented with building portfolio views so we can see stuff in real-time. In some ways, it's okay. In some ways, it's just a little lethargic for our purposes.
We'd like to be able to manage things in real-time and by looking at stuff. We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it.
For some of the portfolio stuff that we did, the queries were so complicated that it was just taking forever. It was like watching paint dry for the results to come back. We would be in a meeting and then we'd hit a refresh and you're waiting for what seems like an eternity.
The solution could use API integration to take feeds from other tools so that we can read them better. We got one camp using an ITBM tool from ServiceNow. We have Jira running in this other area, and having an API between the two so we could actually collaborate between the two tools. However, API integrations with other tools would be helpful so we could either take data out of it or put data in it, thereby making it more of a data-driven platform that integrates nicer with other platforms. That, I think, would be something I would 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.View full review »
Head of Software Solutions at a tech services company with 11-50 employees
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.
Technical Lead at a mining and metals company with 51-200 employees
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.
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.View full review »
Software Test Engineer at a financial services firm with 10,001+ employees
It's totally sufficient to cover our use cases right now. I have no gap at the moment.
There is always a bit of a performance problem. It's a bit slow to load the whole data. When I load those dashboards onto Confluence, it always takes quite a bit of time to get all the data in Confluence. It's a lot of queries.
The only thing that was bothering me was the performance issues where it was very slow.View full review »
Software Engineer at a financial services firm with 10,001+ employees
Jira could be simplified and integrated more with standard corporate communications tools. Say, for example, we have one indication of Jira in Confluence. So if we type a Jira ID into Confluence, it gives us all the information about the Jira profile. I would like to see this feature integrated with email platforms so we can just put our Jira ID or Jira link into an email and get all the details automatically. This kind of integration and automation would be helpful.
I'd also like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile. It's not something for the business side, but developers can track what work is finished and what still needs to be done. Jira could integrate better with Jenkins, which isn't fully supported on the Jira dashboard yet. I think it would be good to monitor the build's progress directly. That way, we don't have to attach it. We can do it from the background. Some workflow customization would also be good.View full review »
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.
IT Project Manager at Gravity Diagnostics
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.View full review »
It is good for single projects, but if you have to manage the portfolio level of the projects, they have a few add-ons that we need to buy and integrate. They can improve this part to manage it in a better way.
It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free.
There could also be some additional reports.View full review »
I would like our clients' IT group to be able to have oversight without setting up agents. We're managing tickets, and I'd like their IT group to see everything we're doing without having to set them up as agents. There should be a better way of managing their users. I've got such requests, but Jira is expensive, and it is difficult to pay an agent fee for somebody else to view these tickets. Currently, the only way in which I can do that is by setting a user up as an agent, and it becomes cost-prohibitive. They need to do a better job on ticket viewers.
If they had a customizable dashboard, it would be great. There should be one with a public URL so that I could share it amongst other viewers. This is the beauty of Smartsheets. With Smartsheets, I'm able to have a customized dashboard. I can bring everything into Gantt charts for budgeting, performance, etc. There is one point of accessibility for our clients so that they can see the program in a snapshot and get whatever assets they need. I love that about Smartsheets, and I wish Confluence had something similar.View full review »
Project Manager at a consultancy with 201-500 employees
Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people. However, I cannot state definitively if this situation owes itself to the way our team put the site together or to something administrative. When clicking the back button it would take the person to the wrong page, not to the one he desires. One would actually have no choice but to browse back to the portfolio and to find his group again and open it. Again, it is not clear to me if this problem lies with Jira or with the way our team laid out the site.
Vice President Quality Management at a financial services firm with 501-1,000 employees
The reporting needs to be better. Being able to do some test management would be useful. In the tool, it would be ideal if they could give you some out-of-the-box reports for things like requirement coverage and regression and things of that nature.View full review »
Agile Software Architect at a computer software company with 11-50 employees
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.View full review »
The next-generation software projects are very easy to use, but they lack a lot, and I found quite a few bugs. There are some really basic things that you still cannot do. For instance, setting a due date for a task that you create as mandatory is still not available. That's a bit of a blocker because people, especially those who are not technical, are not going to add anything if it's not mandatory. It's going to be difficult to teach them that they should do it anyway.
I'm trying to integrate these tools, and I'm trying to open them to different types of teams with different types of people. What I've found is that I read about a macro (App) or about a rule and think that it is what I need, but then find that things are not available for the cloud version. There are some features that are available only in the server version and not in the cloud version. I found a couple of add-ons that we were really interested in, and we couldn't use them because we're in the cloud version.
Sometimes when I tried to set up some macros/add-ons/apps, they didn't work well or were not flexible at all. For instance, you can add only one Excerpt macro to a specific page. And in the that area you cannot have a table, which means you cannot excerpt a table, only content. In general, if you follow the instructions they give you, it works, but when you try to adapt it to your actual needs, it often doesn't work anymore.View full review »
Sr. Manager (TCoE) - ALM Platforms & PO &T IT at a pharma/biotech company with 5,001-10,000 employees
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.View full review »
Programme Manager - Major Programmes Office at a financial services firm with 5,001-10,000 employees
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.View full review »
IT Manager at a government with 10,001+ employees
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.View full review »
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.View full review »
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.
Test Manager /Architect @ Testing Practice at a tech services company with 10,001+ employees
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.
It would be ideal if they could simplify or give more connectors. We need APIs to connect with Jira and they need to be automatically updated in Jira. While the APIs provided by Jira do some work, we'd like them to do more. There needs to be more integration and connectivity.
Atlassian has another product that handles code review. It would be nice to have this in Jira as well or to have it more readily integrated.View full review »
IT Service Manager at a financial services firm with 501-1,000 employees
It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great.
There are a few small functions that we are missing in it. For example, you cannot rate a ticket. If you would like to use a rating for a ticket, you cannot give stars or something like that.View full review »
Business Analyst at a construction company with 1,001-5,000 employees
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 would suggest Jira makes the format compatible with Microsoft Word. Currently, when you copy and paste something from Jira, such as tables, it won't be the same when you copy it into a Word file. There are formatting issues.
If you have 70 or 100 stories, it doesn't work to copy and paste or export each one individually. There needs to be better configuration at a categorization level.
There needs to be a way to export a user story.
By default, Jira is epic and story only. It would be ideal if there was a different categorization between the two. It would be nice if there was a third story option.
There should be a plugin for test cases.
If the solution doesn't have third-party plugins for some features, they should add it into the main offering to make it more complete.View full review »
Manager at a computer software company with 201-500 employees
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.
Chief Software Architect at a tech vendor with 11-50 employees
For me, the solution is too complicated as it has too many features. It would be nice if they could streamline things.
They can make it a little bit better in terms of the user interface. Some things are very scattered. It is a bit confusing. They developed a new user interface, and I cannot follow the changes. There's documentation, however, it's not so good.
The solution has a pretty steep learning curve. It would be great if they could lessen the learning curve by providing more templates and ready-made options for new users to take advantage of.View full review »
Consultor Funcional SAP at a computer software company with 10,001+ employees
I alternate Jira with Excel. I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira.View full review »
Chief Architect / Owner at a security firm with 1-10 employees
They are not supporting in-house servers anymore and I think I've got until January to port this to something else. The issue is not that it is difficult to move Jira to another server, but we have a relatively large database on an SQL Server that Jira either uses or created and we do not want to lose that data.
We are not a very large company so that is a problem. A lot of our business is on Azure and I would prefer to have an Azure solution for our software management. At the moment, I'm trying to figure out how to move Jira over to Azure on our servers. As a small company, we just don't have a lot of time to solve those kinds of problems. So we may end up moving to something else if it turns out to be more difficult than we can handle.
Everybody has to make business decisions and obviously, right now, we're not in that sweet spot for them. But, moving onto the cloud has its advantages too.
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.View full review »
IT Business Analyst at a healthcare company with 1,001-5,000 employees
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.View full review »
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.View full review »
Head of IT Enel X Digital Hub at a energy/utilities company with 10,001+ employees
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.View full review »
There are many areas where improvements can be focused.
There's a really steep learning curve for configuration. I'd like them to simplify all of their configurability yet not remove the configuration options.View full review »
It should be connected to ServiceNow. We use ServiceNow for deployments from our test environment to QA, then to production. If it was linked to ServiceNow, it would be perfect — it would be more integrated. Still, at least we can link our test scenarios, specs, and the tickets themselves so we can track the requirements — that's good. We have to use ServiceNow separately to deploy and move corrections from one environment to another.
There are a lot of features that need to be added on top of Jira for management, sprint planning, and agile topology for project management. My project manager says that there are not a lot of features for project management in the agile mode. They have to buy other products to put on top of Jira to be able to properly manage and to track what people are doing.View full review »
Senior Scrum Master at MobilFlex
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.View full review »
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.View full review »
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.View full review »
Solutions Architect with 11-50 employees
Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it.
Jira is one of the best software applications for project management and budget tracking, but it does have some issues, as follows:
- Firstly, the filtering feature can be improved to some degree.
- Because JIRA has so many features, it may take some time to obtain a general knowledge of each one.
- In order to enhance adoption in small and medium businesses, the cost should be improved.
- I believe it will be difficult for new users to understand.
- There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported.
Enterprise Architect at a transportation company with 10,001+ employees
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.View full review »
Release Engineer at a computer software company with 11-50 employees
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.View full review »
I prefer Azure DevOps and Microsoft Ecosystem to Jira.
I consider Azure DevOps to be more user-friendly and to provide a better user experience. I feel Jira to be a bit difficult to work with. I specifically recall that i encountered difficulties with Jira when I wished to receive or generate a report. Azure DevOps offers a simpler and more user-friendly panel than Jira. Jira's reporting panel is not user-friendly and a bit on the difficult side. Azure DevOps also offers more options for generating queries and reports, especially when it comes to great dashboard visualization capabilities for the monitoring of one's project. This poses a big problem with Jira, as Azure DevOps does a better job of providing this feature.
I find the dashboard to be Jira's most problematic feature. I do not like it and feel Jira is troublesome when it comes to visualizing the reports. These should be improved.
Azure DevOps offers more simplified processes, maintenance and development than Jira.View full review »
Sr Consultant at a financial services firm with 1,001-5,000 employees
It is not intuitive. It was hard for me to understand how to use it right away. It would be ideal if they could make the solution more user-friendly so that it is easier to pick up.View full review »
It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira.
I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports.View full review »
Senior Front End Engineer
So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now. We had gotten used to the old interface, so things changed, we felt an initial discomfort. That's the only thing. Otherwise, there is nothing I dislike about JIRA.
Director at a comms service provider with 1,001-5,000 employees
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.
Senior Software Engineer at a tech services company with 5,001-10,000 employees
Its search and reporting can be improved. They are already nice, but they can be further improved.
Software Engineering & Quality Manager at a leisure / travel company with 201-500 employees
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.View full review »
While it's very powerful, it's very complex sometimes. You can do many fancy things and have connections between features. With so many options, it's easy to get lost and it's not as easy to be on top of all the features and changes. In that sense, ServiceNow is easier to keep up with. Its configuration is more complex than ServiceNow.
The interdependencies between objects sometimes are not easy to trace back and to have a clear view of. That's why starting with small configurations is very important; we don't create very complex structures between objects in Jira. That said, sometimes when updating a history that was linked to an epic we would not understand why the epic didn't change when we changed the history. The relation sometimes can become complex. This is not a problem of Jira per se, it's a problem of how you configure Jira.View full review »
We'd like to see more collaboration tools implemented within the product itself.
The product needs to allow for more communication between individuals and teams.
The solution could always use better reporting.View full review »
RPA Developer/Consultant at a tech services company with 1,001-5,000 employees
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.View full review »
Senior Technical Project Manager at a financial services firm with 10,001+ employees
Although this is a somewhat old-school approach, we'd like to see some common building block approaches to certain things. We do a lot of coding and swapping things because there's a lot of common non-functional capabilities we have to share based on our own company policies. In that sense, it would be helpful to have some sort of modular building blocks that are in some of these up-and-coming extensible capabilities, like how you interface the next level of security scanning code or cloud to cloud capabilities, anything like that would be an improvement. These are expensive things to build and give out for free. At least knowing what's in the headlights for the products together with some good specific industry demos would help, whether related to the financial sector, healthcare sector, whatever. There isn't a lot of that; as things stand, they're generally offering demos with people talking about how you could have a secure way of developing a code for a HIPAA mixed standards or whatever. More documentation on how to precisely use the solution, particularly in a given industry sector, would be helpful.
We use a lot of third-party monitoring and although the extensibility is there, a monitoring tool suite as you get in production would be helpful.
Sometimes, it gets a little bit difficult to find the exact issues for people, but the search works fine in general.
The Classic UI is a little bit messy. UX experience is also a little bit messy and is not according to the expectation of a tech user.
If I click on an issue, that issue opens on the side. It shouldn't be like that; either it should open as a pop-up so that I can see where it is opening or it should open somewhere else, maybe as a pop-up or a new page. The view on the side is a bit of a hurdle. The UX needs to be improved.
Good use of Kanban technology should be there. Right now, it is mixed with Scrum technology, but that's not very necessary.View full review »
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.View full review »
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.View full review »
JIRA could simplify the query mechanism. Running a query for tasks, stories, and so on is far easier in TFS. The algorithm is easier. In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members. So that is one area where JIRA has some room for improvement.
Software Engineer at a tech services company with 1,001-5,000 employees
They could probably improve the integration with some of the automation tools and provide a specialized user interface suitable to their requirements.
Technical Lead at a retailer with 10,001+ employees
We have been working on integrating Jira with Confluence for the past months but it is not yet working. Having more seamless integration with Confluence would really help us track our product management activity and other product details in one place.
Integration with BitBucket would allow us to have a better deployment process.View full review »
Agile CSM - Sr. Scrum Master at a energy/utilities company with 1,001-5,000 employees
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.View full review »
Partner at a consultancy with 11-50 employees
I'd like the solution to be more secure.View full review »
Consultant at a tech services company with 1,001-5,000 employees
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.View full review »
Senior Consultant at a consultancy with 1-10 employees
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.View full review »
Software Engineer at a tech services company with 501-1,000 employees
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.View full review »
Microfocus Solutions Engineer at a tech services company with 11-50 employees
We're more focused on other solutions. Jira could be more, for example, like Micro Focus, which is what I mostly work with currently.View full review »
Partner at a tech services company with 1-10 employees
When I was managing projects that started from epics and moved to multiple tasks, I found that the integration of epics and user stories could have been a little easier. I've seen people struggling to use that aspect of Jira. I think that there is some ease of use that could be brought in to improve certain things.View full review »
Jira could be more user friendly. When I started using it, I faced difficulties in different project selections and there were issues with bugs. It was not straightforward. I feel it could offer an improved user experience. I have a small issue that whenever I log out there's a bug and for a fraction of a second, I'll get a notification that then disappears before I can do anything about it.
Lecturer at a university with 1,001-5,000 employees
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.View full review »
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.
Sometimes it takes time to load the data.View full review »
Cloud Global Director at a comms service provider with 10,001+ employees
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.View full review »
IT PMO Project Leader at a consumer goods company with 10,001+ employees
The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough.
So far, I've only used the project management parts. We are examining resource planning and sample plugins for the product. From my point of view, resource planning is a little bit hard to link with project management. Sample plugins are another part of the system, and we need to link it with project management in the BigPicture screen, which is a little bit hard. It would be valuable for us if we can do resource planning in BigPicture as well. Currently, it is another plugin, and you can only plan based on the people and not projects, and you cannot link it, as far as I know.View full review »
Owner at a media company with 51-200 employees
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.View full review »
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.View full review »
Senior Analyst Engineer at a financial services firm with 10,001+ employees
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.View full review »
Director at a computer software company with 10,001+ employees
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.View full review »
Middle Manager at a tech services company with 201-500 employees
Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too.View full review »
IT Planning and Control Manager at a financial services firm with 1,001-5,000 employees
It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios.
We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration.View full review »
Cloud Architect at a computer software company with 1,001-5,000 employees
They could improve the solution by having a multiple project dashboard to be able to manage many projects KPI's at once, this would really be helpful.
In the next release, I would like to see task creation management simplified and overall usage streamlined for new users.View full review »
Quality manager at a computer software company with 201-500 employees
Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows.View full review »
Global Senior Manager at a logistics company with 10,001+ employees
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 reporting capabilities, specifically customized reports, should be improved. The out-of-box reports don't meet our needs. We are big into customizing our reports, and being able to do ad hoc reporting would be good.
Lead Consultant at a computer software company with 10,001+ employees
The solution could be improved with respect to how the end-to-end is managed from product backlog creation until test completion. Although it can be customized, if there was a standard out-of-view box feature or a workflow, that would be helpful. There are features that are currently not out of the box and lack end-to-end traceability, such as the business value of a particular feature. It would be great if that were included.
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.
Manager, PMO at a educational organization with 1,001-5,000 employees
In general, it is not user-friendly.
For a non-technical person to use, Jira is not intuitive. If you are a developer it's fine, but we are trying to get other technical people in to look at tasks or to update a task, move it from one sprint to another sprint and it takes more effort than I would like.
I would just like to see it easier to use, and I would like the workflows to be less complex to do what we need them to do.View full review »
I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues.View full review »
Owner at TRS
Based on the feedback from my admin, it is sometimes difficult to find some of the features. It is not a big deal, but its configuration interface can be improved to make it easy to find things.View full review »
Senior Software Engineering Manager at a comms service provider with 10,001+ employees
We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface.
The solution could improve the Agile reports. They do have quite a bit of reports already, but additional reports would be a benefit.View full review »
Service Delivery Manager at a tech services company with 51-200 employees
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.View full review »
There are too many restrictions in Jira. In DevOps, you can access the dashboards easily, but in Jira, you should have more administration rights. In our organization, there are some restrictions on creating dashboards and other features. Everything should be accessible with all access rights for everyone.
Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira.View full review »
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.View full review »
The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again.
In an upcoming release, they should improve the user management features. For example, when I want to monitor a project as a CEO I do not want all the details but enough that I can understand. Additionally, these features should be accessible to me by mobile.View full review »
Senior DevOps/Build Engineer at a tech services company with 10,001+ employees
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.View full review »
Director of operations at a computer software company with 1,001-5,000 employees
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.View full review »
Deputy Director - Network/Systems and Support - IT department (USJ) at a university with 1,001-5,000 employees
It's a very customizable solution, but as a customer, we're always looking for additional customization. There could be better customization in future releases. If we changed from Atlassian to another product, we would look for a customizable solution.View full review »
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.View full review »
CEO at a transportation company with 1-10 employees
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.View full review »
Lead architect at a computer software company with 10,001+ employees
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.View full review »
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.View full review »
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.View full review »
IT Process Engineer at a tech services company with 51-200 employees
The solution could be more user-friendly.View full review »
IT specialist at a construction company with 10,001+ employees
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.
Senior VP at a financial services firm with 1,001-5,000 employees
I don't really have any areas for improvement. It works very well for what it is. I don't have any suggestions.
We'd like to see Jira have more integration with a development ID.View full review »
Java Architect at a healthcare company with 11-50 employees
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.
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.View full review »
Director Data Analytics at a tech services company with 201-500 employees
If you're not a technical person, it might not be very user-friendly.
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.View full review »
The help desk and services management features are in need of improvement.View full review »
The main area for improvement is the high cost of the product.View full review »
Technial Lead at a transportation company with 1-10 employees
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.View full review »
Executive Vice President at a financial services firm with 10,001+ employees
The history with Jira is that it is a bit complex for many users.
There are too many features.
The user interface is complex.View full review »
Senior Software Engineer
It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story.View full review »
QA Supervisor at a financial services firm with 10,001+ employees
The solution could improve by having its own tool for quality lifecycle management.View full review »
Cost could be improved. The pricing is quite high. I could also see there being a need for improvements in software product management, project planning, and DevOps.View full review »
Project Manager at Ibermatica
The integration and management features need to be improved.
When you first start to use the interface, it is confusing.View full review »
Project Manager/Product Owner at a tech services company with 11-50 employees
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.View full review »
Delivery Head IT & IS at a non-tech company with 10,001+ employees
Line Technical Agent at a comms service provider with 1,001-5,000 employees
It should be less expensive.View full review »
CEO at a tech services company with 11-50 employees
The performance could be improved in the future.View full review »
Project Management Officer at a computer software company with 501-1,000 employees
I think support could be improved, in particular it would be helpful having a login for the support team.
Devops Engineer at a financial services firm with 1,001-5,000 employees
The solution needs more integrations with Azure DevOps OnPrem.
I can't speak to any missing features. It has what we need overall.View full review »
Test Specialist at a tech services company with 10,001+ employees
The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details.
I don't think Jira has a copy/paste option for emails. I know that you can attach emails, but I don't think there is a copy/paste option.View full review »
Senior Consultant/Engineer at a government with 1,001-5,000 employees
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.View full review »
Chief information technology officer at a financial services firm with 11-50 employees
For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great.View full review »
MTS IV at a transportation company with 5,001-10,000 employees
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.View full review »
The filtration could be better.View full review »
Technical Content Writer at a computer software company with 51-200 employees
I'd like to see a more stable product with more integrations, as new products are coming on the market daily.