Try our new research platform with insights from 80,000+ expert users

Pros & Cons summary

Buyer's Guide

Get pricing advice, tips, use cases and valuable features from real users of this product.
Get the report

Prominent pros & cons

PROS

Jira enables teams to efficiently track and manage projects, offering customizable workflows and reports for seamless agile project management.
The tool supports integration with other Atlassian products, providing transparency and streamlined communication across geographically diverse teams.
Traceability from requirements to test cases and changes is a key feature, making it invaluable for QA and development tracking.
The tool's flexibility allows customization to align with unique team processes and workflows, making it suitable for a variety of organizational needs.
Jira's adaptability with boards such as Scrum and Kanban enhances task and backlog management, improving productivity and time management.

CONS

There are regular reports of slow performance and downtime, causing loss of comments and impacting productivity.
There is a lack of integration with popular tools, causing challenges in maintaining a seamless workflow.
Customization features in Jira are complicated, and administrators find the setup challenging and cumbersome.
Reports and out-of-the-box configurations are limited, requiring additional plugins and workarounds to meet specific needs.
The price of licensing is considered high compared to alternatives, generating concerns over cost-effectiveness.
 

Jira Pros review quotes

it_user72771 - PeerSpot reviewer
Info Sec Consultant at Size 41 Digital
Jun 1, 2017
Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes.
MM
Partner at a manufacturing company with 501-1,000 employees
May 29, 2017
The configurable workflows and boards make it easy for us to execute and oversee our own unique process.
it_user678153 - PeerSpot reviewer
Agile Coach & Sr. Project Manager at a retailer with 10,001+ employees
Jun 5, 2017
The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features.
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
882,637 professionals have used our research since 2012.
it_user607749 - PeerSpot reviewer
Manager, Live Production at a computer software company with 1,001-5,000 employees
Jul 6, 2017
I found it super useful, as it is customizable for different teams and users.
it_user535656 - PeerSpot reviewer
Test Manager
Jul 31, 2017
​One of the valuable features is traceability from requirements to test cases.
it_user461610 - PeerSpot reviewer
Technical QA Lead in HPE NGA Synchronizer at a tech vendor with 10,001+ employees
Sep 18, 2017
For QA, the most interesting for me are boards, backlog, and filters.
it_user787857 - PeerSpot reviewer
Technical Writer at a tech vendor with 11-50 employees
Dec 12, 2017
JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified​.
it_user809520 - PeerSpot reviewer
QA Automation at a tech vendor with 501-1,000 employees
Jan 28, 2018
The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components.
it_user812835 - PeerSpot reviewer
Sr. QA Manager with 501-1,000 employees
Feb 2, 2018
It gave us control over all test artifacts in one place, along with easy traceability, mapping between stories, bugs, test cases, and test cycles.
it_user839079 - PeerSpot reviewer
Fachbereichsleiter with 10,001+ employees
Mar 22, 2018
It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it..
 

Jira Cons review quotes

it_user72771 - PeerSpot reviewer
Info Sec Consultant at Size 41 Digital
Jun 1, 2017
There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed.
MM
Partner at a manufacturing company with 501-1,000 employees
May 29, 2017
There are some minor quirks, such as zero-point stories not appearing in the portfolio scope.
it_user678153 - PeerSpot reviewer
Agile Coach & Sr. Project Manager at a retailer with 10,001+ employees
Jun 5, 2017
Ease of administration and customization. It is really clunky in this area.
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: February 2026.
882,637 professionals have used our research since 2012.
it_user607749 - PeerSpot reviewer
Manager, Live Production at a computer software company with 1,001-5,000 employees
Jul 6, 2017
The following definitely need improvement: UI, speed, and mobile app functionality.
it_user535656 - PeerSpot reviewer
Test Manager
Jul 31, 2017
I would like to see test execution modules.
it_user461610 - PeerSpot reviewer
Technical QA Lead in HPE NGA Synchronizer at a tech vendor with 10,001+ employees
Sep 18, 2017
Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches.
it_user787857 - PeerSpot reviewer
Technical Writer at a tech vendor with 11-50 employees
Dec 12, 2017
I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA.
it_user809520 - PeerSpot reviewer
QA Automation at a tech vendor with 501-1,000 employees
Jan 28, 2018
I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.
it_user812835 - PeerSpot reviewer
Sr. QA Manager with 501-1,000 employees
Feb 2, 2018
It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins.
it_user839079 - PeerSpot reviewer
Fachbereichsleiter with 10,001+ employees
Mar 22, 2018
I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be.