We changed our name from IT Central Station: Here's why

Jira Pros

Product Manager at a insurance company with 10,001+ employees
You no longer need to email people. You can mention them right in Jira and have conversations there.
View full review »
VN
Senior PM / Scrum Master at a financial services firm with 1,001-5,000 employees
It was very easy to learn Jira. As a scrum master, I run daily stand-ups, and they are run directly from Jira. The feature that I really love in Jira is called Issue Navigator. It allows me to customize how I want to show the user stories within Jira to my squad.
I can use Jira Query Language (JQL) to write queries to see the stories that are there for the current sprint. I can also sort them by assignment. I also use Jira is for burndown charts, which give an indication of how efficiently the squad is performing. I also use the Active Sprints function and a feature called Planning Poker.
View full review »
Senior Principal Engineer at a consultancy with 1-10 employees
The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out.
View full review »
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,327 professionals have used our research since 2012.
KV
Product Engineering & Operations Director at a tech services company with 10,001+ employees
In terms of the general way that the tool functions, it seems like it's a pretty good fit-for-purpose for what we're trying to do. We've never thought about replacing it with another technology.
View full review »
Consultant at a pharma/biotech company with 10,001+ employees
It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want.
It also works well with all the integrated tools that you buy.
View full review »
AO
Head of Software Solutions at a tech services company with 11-50 employees
It's really smart how they connected these third-party vendors into their own marketplace. You can create and add apps. Anybody can do it.
View full review »
PO
Technical Lead at a mining and metals company with 51-200 employees
With the help of Jira, tasks are less likely to remain stagnant for a long time. We always see them somewhere on the board.
View full review »
Global Client Support Operations Manager at kyriba
This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page.
View full review »
PM
Software Test Engineer at a financial services firm with 10,001+ employees
I was able to do real-time reports myself without having to wait for data import.
View full review »
KH
Software Engineer at a financial services firm with 10,001+ employees
When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool.
View full review »

Jira Cons

Product Manager at a insurance company with 10,001+ employees
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.
View full review »
VN
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. When Epic Link's background color is a dark color, it effectively becomes unreadable. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view.
There needs to be an easier way to capture a few metrics. 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.
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. 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.
View full review »
Senior Principal Engineer at a consultancy with 1-10 employees
From a very software-centric or a lead developer standpoint, there should be the ability to work at multiple levels. You have epic stories and use cases or epic stories and tasks. It would be nice to be able to have multiple levels of stories and multiple levels of epics work with it. It's lacking a little bit there, and this is the big thing for me because it makes it difficult to do a real sprint when you're limited to one story per epic. It's really hard to isolate tasks at multiple levels to match the type of use cases you normally do. That's the biggest difficulty. Other than that, they've been improving year to year, and every version seems to have a level of improvement.
View full review »
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,327 professionals have used our research since 2012.
KV
Product Engineering & Operations Director at a tech services company with 10,001+ employees
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.
View full review »
Consultant at a pharma/biotech company with 10,001+ employees
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.
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.
View full review »
AO
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.
View full review »
PO
Technical Lead at a mining and metals company with 51-200 employees
There needs to be easier integration with third-parties — personally, this is the biggest issue for me.
View full review »
Global Client Support Operations Manager at kyriba
Jira has recently updated their UI, but more can be done to make it even better.
View full review »
PM
Software Test Engineer at a financial services firm with 10,001+ employees
There is always a bit of a performance problem. It's a bit slow to load the whole data.
View full review »
KH
Software Engineer at a financial services firm with 10,001+ employees
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.
View full review »
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,327 professionals have used our research since 2012.