Skip to main content
TrustRadius
Jira Software

Jira Software

Overview

What is Jira Software?

Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.

Read more
Recent Reviews

Jira is a Saviour

9 out of 10
March 08, 2024
Incentivized
Jira Software is a project management tool that is widely used by various teams in our organization to manage their projects and tasks. …
Continue reading

TrustRadius Insights

Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Standard

$8.15

Cloud
per month per user (minimum 10)

Premium

$16

Cloud
per month per user (minimum 10)

Data Center

$44,000

On Premise
per year 500 users

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.atlassian.com/software/jira…

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $81.85 per month 10 users
Return to navigation

Product Demos

JIRA Project Management Tutorial for Beginners (2022)

YouTube

The full overview: Roadmaps in Jira Software

YouTube
Return to navigation

Product Details

What is Jira Software?

Jira Software is a project management tool software used by agile teams and supports any agile methodology, be it scrum, kanban, or a team's own unique flavor. From agile boards to reports, users can plan, track, and manage agile software development projects. And since not every team works the same way, Jira Software allows teams to customize workflows, permissions, and schemes to match the unique needs of each team.


Jira templates also support use cases in enterprise marketing management, and projects to support operations, design HR, and enterprise marketing management.


With Jira Software, teams are able to:

  • Track versions, features, and progress at a glance
  • Re-prioritize user stories and bugs
  • Estimate stories, adjust sprint scope, check velocity, and re-prioritize issues
  • Estimate, track and report on story points; become more accurate
  • Report on agile metrics to provide real-time, actionable data on team efficiency, quality, and overall performance
  • Integrate with all the tools their dev team is already using, from the rest of the Atlassian suite (Bitbucket, Bamboo, Fisheye, and Crucible) to other popular developer tools on-premise or cloud (e.g., GitHub and Jenkins).
  • Provide greater flexibility to curate which teams have access to which information with sprint and project-level permissions
  • Flexibly tailor Jira tasks and their workflows to a specific team's use case
  • Extend Jira with over 1,800 apps from the Atlassian Marketplace to fit any capability not provided by default

Jira Software Videos

Jira in a Nutshell Demo Video
Jira Software is a software development project management tool of sorts, that tracks progress, offers up project reports, and gives a great roadmap view to understand workloads and deadlines better. In this video, the TrustRadius team goes over Jira Software pricing, top feat...
 Show More

Jira Software Competitors

Jira Software Technical Details

Deployment TypesOn-premise, Software as a Service (SaaS), Cloud, or Web-Based
Operating SystemsWindows, Mac
Mobile ApplicationApple iOS, Android

Frequently Asked Questions

Jira Software is a project management tool from Atlassian, featuring an interactive timeline for mapping work items, dependencies, and releases, Scrum boards for agile teams, and out-of-the-box reports and dashboards.

Jira Software starts at $81.85.

Bugzilla, Podio, and Zoho Projects are common alternatives for Jira Software.

Reviewers rate Support Rating highest, with a score of 8.8.

The most common users of Jira Software are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(3244)

Community Insights

TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!

Easy-to-use tool with minimal learning curve: Users have found JIRA to be an intuitive and user-friendly tool that requires minimal effort to learn. Several reviewers mentioned that they were able to navigate through the platform easily and quickly adapt to its features.

Seamless collaboration through integration with other tools: Many users appreciated JIRA's ability to integrate with various plugins and add-ons, enabling seamless collaboration across different teams and departments. This integration allowed for enhanced productivity by bringing together different tools into one centralized platform.

Flexibility of customization: The flexibility of JIRA in terms of customization was highly regarded by users. They mentioned being able to customize bugs, tasks, and stories based on the specific requirements of their projects. This flexibility helped them tailor JIRA to their unique project management needs.

Confusing and overwhelming user interface: Many users have expressed frustration with the confusing and overwhelming user interface of JIRA. They find it difficult to efficiently complete tasks due to a lack of intuitive navigation and cluttered design.

Complexity and difficulty in customization: A significant number of reviewers find JIRA's customization options to be complex and challenging. It often requires dedicated training to effectively navigate and utilize the software's customization features.

Limitations in reports, charts, and attachments: Users have reported challenges in sharing information within JIRA due to limitations in reports, charts, and attachments. These limitations hinder effective collaboration, communication, and data visualization.

Attribute Ratings

Reviews

(101-125 of 187)
Companies can't remove reviews or game the system. Here's why
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Jira, at a high level, is being used by our technical teams (engineering, support, implementation) to track development efforts, product feedback from our clients, as well as Dev, QA, and production efforts to get our clients up and running. In addition, of course, to tracking bugs in our product. Jira allows us to collaborate across all of our teams as well as keeping us all apprised of the progress of each individual project or longer-term initiative.
  • Tracking projects based on assignee (ie: the person who needs to take action on a ticket).
  • Easily seeing how many product tickets are open at any given time.
  • Planning and road mapping of your product, Jira makes it very easy to track priority with development effort, you can display it easily on a map.
  • I'd like to see merge fields be slightly easier to use, but you can still format everything really nicely in comments, so it isn't a big problem.
Jira is well suited for small to medium teams working on a distinct package of software products. My only experience is with teams using Jira with <100 people, but I don't imagine it would differ tremendously on larger teams. Jira allows you to easily separate out product areas if you have multiple lines of product, and it integrates seamlessly with our chosen support platform, Jira, as well as our CRM, Salesforce.
Amrinder Arora | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
JIRA is used by the entire BizMerlin team for design and development of the product roadmap. Product managers add items to the backlog as well as various sprints. Test Preparation, QA, code review, development, everything is controlled through JIRA. Scrum masters do their daily stand-ups and record notes, as well as ensure the issues are being updated correctly via comments and status transitions.
  • When you want a configurable workflow for different issue types
  • Showing the entire sprint progress at a glance in the burndown (or burnup) chart
  • Ensuring every team member (even a new one) knows the steps that an issue has to take before closure
  • Workflows and schemas are sometimes really difficult to understand. You learn it one time and it works fine for 6-7 months. When you need to modify it, it seems you need to learn it ALL OVER again.
  • Left hand navigation panels sometimes need to be collapsed and expanded multiple times.
For any kind of software project (unless it is a very short 1-2 week project), having a sophisticated project management tool like JIRA is going to payoff. JIRA has enough bells and whistles that even as your project evolves in terms of processes, you will be able to track it correctly in JIRA, including any items that need to be tracked.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
JIRA is being used as an overall tracking tool for application development. Requests for new enhancements/projects may be placed in the system or defects may be tracked. IT managers also use the tool to assign tasks and to check hours booked to a project or request. Management reporting also comes from the application and is used for capacity planning and resource management.
  • Great tool for agile development
  • Allows flexibility to build out workflows that map to your company's internal processes
  • Flexibly reporting and build out by team
  • Make certain the full end to end processes are documented - changing flows will impact the lineage of your data
  • Make certain someone on the team has JIRA experience or have a vendor support you in the implementation
  • Look at full functions offered out of the box and understand additional plug-ins that may be needed.
Good for large and small teams. It is just important to make certain it is implemented and used consistently across all teams. Generally it is a process difference that causes issues - not JIRA itself. Support is good, but in several areas it is easy to design yourself into a corner with process flows and approvals.
Score 9 out of 10
Vetted Review
Verified User
JIRA is being used across the organization by a wide array of users. We use it for issue tracking and sprints as well as as a product pipeline. It allows us to adequately track and communicate easily with other JIRA users in the organization and accomplish many different things quickly and effectively.
  • JIRA is great for tracking issues
  • It allows for excellent communication with other JIRA users
  • It's easy to search and navigate the platform
  • Administration of JIRA is very easy and straightforward
  • Documentation is generally pretty good as is JIRA support
  • Sometimes the documentation is a bit tricky to find depending on what version you're running
  • Troubleshooting complex issues when you use multiple plugins can be difficult
It's great for issue tracking and sprint planning. The workflows are excellent and very good for those types of use cases. With the amount of plugins available, you can accomplish just about anything you would want to do and integrate with many different platforms.

There are different roles and types of access, so you can define access at a pretty granular level.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
JIRA ALM is one of best ALMs available in the market today. The rating for the overall user interface would be 4/5. Mainly because of it's seamless depiction of all the project related milestones in a neat and quickly understandable format. The USP of the JIRA ALM is it's defect tracking mechanism. The well laid out user interface allows the the development team to quickly access the defects and update, view and review the status of the defects. The implementation of JIRA ALM has really helped me and my team in optimizing the overall project development lifecycle. Would rate the JIRA defect tracking mechanism a solid 5/5 rating.
  • The defect management and tracking mechanism is one of best in the industry.
  • The cost for the software licensing could be improved upon.
Very positive. Excellent, easy to use tool for managing development projects. Tracking, creating and assigning sprint tasks was user friendly. Flexible viewing configurations are great.
July 16, 2018

JIRA-Easy to track

Score 10 out of 10
Vetted Review
Verified User
Incentivized
The complete organization uses JIRA to track the issues or create user stories for developers.
  • Managing workflow is too good.
  • Miscalculates the pending minutes some times.
It is easy to create, assign, track workflow and store comments and also sending emails on the ticket is really helpful.
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Jira is used primarily by IT department as our software development tool for tracking all work. Recently our marketing and claims department has started to use it as well. We also use the Dashboards to highlight our production release items to the rest of the businesses non IT related on a monthly basis.
  • Easy to drag and drop issues to status
  • UI is very good and easy to follow the sprint progress
  • Dashboard features are good
  • Issue detail view can be a little limited, would like more room to configure
  • Change the status of issue in all issue views
  • Increased functionality on dashboards, allow text field boxes
Very well suited to handle all software development tracking for small or large teams
Excellent for IT production release management, we use a TFS plug in for our code
Works well when paired with Confluence
Works well when paired with Service Desk
Non IT departments have a hard time using it since they don't typically work in agile
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use JIRA to track and manage all bugs and tasks relating to the engineering teams in the company.
  • Great for engineers to track issues, bugs, problems, etc.
  • Helpful for collaboration on bugs and great for managing sprints.
  • Definitely not the prettiest or most intuitive interface. Very much feels like it was built by an engineer.
  • My biggest annoyance is that I get emails for updates to a bug's comments far too frequently. As in, someone will be editing a task and I'll get 5 emails in the course of them simply typing something out or making updates to the task. These things should be aggregated and there should be a time delay on when the emails reach me.
If you do any work with engineers, be prepared to understand and know how to use JIRA.
Poorva Naswa | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Logging and tracking issues in the project. I also use it as a way of noting down ideas as they arise. I don't have time to do most things as they are thought of so it is great for logging for future reference. When I complete one task or project, I visit my Jira queue and see what I can do next depending on priority and time constraints. It is a great way to get some quick wins done if I only have a short time so I can clear the queue a bit before taking on my next big project.
  • I personally like the ability to track where issues and task are, how much work has been completed on them and what the estimated time remaining is.
  • Easy to interact with a task. Easy to get into the task for the bug fixes and report it to the higher level through the spontaneous notifications.
  • I like how JIRA helps teams organize themselves.
  • I can't say anything that bothers me about JIRA.
  • The price is little bit high.
Using JIRA helps us to keep everyone on the team on the same page. The ability to be able to track the progress of everyone on the individual stories, spikes, and epics that they are working on helps to give everyone a sense of accountability and community in a more business-oriented fashion.
Richard Rout | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use JIRA as a project management tool. We use it to manage our backlog of tasks, plan our sprints and organize who works on what. We use their reporting to get metrics on how well the team and individuals are performing. JIRA is used across the entire organization to manage all forms of work.
  • Customized workflows - JIRA can be set up to work for any imaginable workflow.
  • Fine grained account control - roles can be created for any type of user access, giving you full control.
  • Nice looking and easy to use UI.
  • Available in SaaS and self hosted.
  • It can be overwhelming. So many configurations and options can make it difficult to manage.
  • It's among the most expensive in its category. Much cheaper options are available and likely do what you need.
  • If your admin configures things wrong, it can be very difficult to use as a user.
JIRA is well suited for companies who need full control over their teams' workflows. If your company has varying teams who work differently and already have a workflow set up in place, JIRA can be configured on an individual team basis to suit your teams' needs.
Score 7 out of 10
Vetted Review
Verified User
JIRA is used for small pilot tests that require rapid iteration on software projects.
  • Highly customizable
  • Dynamic
  • Good integration with a variety of other products
  • High price
  • Not the best UX/UI
  • Difficult to setup
JIRA helps bridge the gaps between product employees and the developers. This system is very easy to learn for technical users, but the non-technical user may have some issues. We only use Jira for quick engagements; for long-term projects, experience may be different.
Flávio Carmo | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
We use Jira to manage all our user stories, all development content, and actions. With this tool, we no longer forget anything in our development cycle.
  • Configurable
  • User friendly
  • Cost for small teams
  • Too many options. Sometimes a configuration has too many steps to be done.
  • Cost to medium teams
  • A large server footprint to local servers (Tomcat is a large memory user)
Is the best tool for all development cycles, waterfall, scrum, kanban, lean-agile, anyone. If you have a business need, like service desk, the Jira Service Desk to is the tool.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
JIRA software is currently being used within our department as an organizational tool. JIRA is being used intermittently across the whole organization, but is not currently a standard. JIRA really helped our team with organization and collaboration as it breaks down work and assignments in a simple and visible way.
  • Easy and efficient way to organize and assign work
  • Allows for the creation of a hierarchy of tickets and work to keep priorities organized
  • User-friendly and cost efficient as an organizational tool
  • Training resources readily available
  • Being able to create epics would be highly useful for better organization and maintenance
  • Being able to split the work, or tickets, between team members would also be useful
  • There is a learning curve which does require time and resources to adapt to the tool
JIRA Software proves to be very well suited for teams looking for a basic organizational tool to track work, assignees and time spent using a ticketing system. It makes it very easy to solidify ideas and track accomplishments. I feel that JIRA is less appropriate when trying to create and track epics or user stories in more of an Agile environment.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use JIRA across all departments, including marketing or customer success. Development teams use Scrum capabilities (sprints, etc.), while the rest of the organization typically uses Kanban boards.
  • Highly customizable
  • Comprehensive workflows
  • Granular notifications
  • Clear UI
  • On-demand version is often very slow
JIRA is suitable for large projects with lots of custom requirements. For smaller projects, I'd recommend something simpler and cheaper.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
The applications are hosted in the cloud. This means you don't have to worry about buying and maintaining your own infrastructure. The service's very reliable, affordable, allow us to do several integrations and fully customizable on all the steps. This product allowed us to easily control, manage and measure all the steps of our development lifecycle.
  • Custom fields.
  • Define several workflows.
  • Collaboration between teams.
  • UI/UX lacks.
  • Performance issues.
This product allowed us to easily control, manage and measure all the steps of our development lifecycle.
Eliz Marvic Melicio Carvajal | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Incentivized

In the software development department of the company, we control projects under the agile methodology. We manage all the development and maintenance projects of our internal applications using JIRA. We control development times and assign priorities to projects.

In addition to this, we receive feedback that comes directly as pending issues in Jira of the users, to more efficiently manage the improvements and failure reports of all applications in use and in the process of testing.


  • It is excellent for the control of development projects under agile methodology.
  • It allows you to reprogram issues, attach images, set subtask to each issue, which later depending on the complexity you can convert into an issue to execute later.
  • By closing each sprint you can graphically view the Burndown Chart, which allows you to analyze with the development group, if the sprint was under what was planned or what caused the deviations.
  • It would be ideal to have among the notifications one that alerts when a sprint is about to finish and still has tasks to do and in progress.
  • The user interface for Jira in the cloud and Jira on server versions should be the same.
  • It should have an integration with the Outlook calendar, iCal or any other calendar so that everyone has calendar programming in a single application.
When you have planning meetings for the development activities, the scrum board is an excellent ally to see the status of the issues and the workload of each developer.

When you need to analyze the month's work of the department, and you rely on a list of issues (where input the issues product suggestions or errors reported by users and those entered by the development team) is not easy to filter to organize them by project and in some specific status, this is to quickly determine the number of issue that you have for example by making one or several projects.
Sourav Singla ,Safe Agilist, CSP,  ICP-ACC, CSM, CSPO, SSM, LSSG | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
It is being used at a program level in the organisation. We use JIRA to track our Agile teams that are [composed] of Scrum and Kanban teams. We use it for tracking epics, stories, issues, tasks, subtasks, production maintenance tracking, and planning.

It provides a good dashboard where higher leadership can look at how things are progressing and ultimately bringing in transparency.

It eliminates the need for individual teams to send weekly or monthly status reports to leadership on progress and what they are involved with. So at team level sprints, stories, epics, sizing, capacity, scrum and Kanban boards are managed and looked at.

  • Requirements are managed very well there which can be captured in the form of epics.
  • Epics, which capture the high-level ideas can be broken down into stories, tasks and sub-tasks.
  • The team can team can raise bugs, capture comments and tag test cases, against each story ultimately bringing end-to-end traceability.
  • Since distributed agile requires more collaboration, JIRA's seamless integration with communication tools like HipChat and Slack allows teams to work collaboratively.
  • JIRA supports customization since each team is unique, you can create your own issue types, modify the workflows, add/remove fields.
  • Standard issue types created in any project are: a) Bug b) Task c) Sub-Task d) Epic e) Support Ticket f) User story
  • User Story workflow can be: a) Backlog b) Ready to Start c) Dev In-Progress d) QA In-Progress e) Ready for Demo All these can be modified based on your requirements.
  • If you are looking for devops implementation, JIRA has support for CI & CD.
  • It can be integrated with Git and Jenkins very well.
  • JIRA supports two kinds of boards, Kanban and Scrum boards. It is very easy to track things using these boards & it also provides ample of charts like reporting options such as burndown charts to help teams plan & replan at every stage in the development life cycle
  • Searching issues in JIRA is very simple through JQL (Jira Query Language).
  • If we would like to perform a complex search JQL allows to find issues from any timeline.
  • The basic version of Jira do not have support for test management, capacity management & release management.
  • So users have to buy various plugins to support these basic functionalities which can prove costly based on team size.
  • Navigation around the UI can be difficult at times
  • Jira is not a simple tool, it requires some training before users can start working on it so some learning curve is involved.

Situations where JIRA is helpful:

1) If our board becomes quite dense and full of issues, it can be difficult to remember all of the issue numbers or track them, so in JIRA we have the option to flag and comment on the issues and the ticket background color becomes yellow which makes the tracing quite easy.

2) Prioritization has become a lot easier with JIRA. It is a one-stop shop for all tasks and projects you are working on. It gives a better look into what each program is working on.

3) When a lot of tasks need to be updated, we can use the “Bulk Change” option present in the right-click menu. It is a good time-saving tool when we have more than 8 tasks to change at once.

4) Many filters can be set in JIRA based on the issues you want to track:

a) Quick filter query to see what is currently scheduled to the sprint. Query: Project = "ABC" AND sprint = ‘Sprint number’ AND issuetype in (Story, Bug) ORDER BY issuetype ASC, status ASC

b) Quick filter query to view the backlog items: Query: Project = "ABC" AND Status = "1.1 Backlog" ORDER BY Rank ASC

Situations where JIRA is not helpful:

1) If your stories have lot of architecture diagrams or documentation you need to integrate it with another Atlassian Tool Confluence & Jira do not have much support for excessive documentation.


2) Even after buying the "Test" plugin, test case management is not that easy & extensible as we have in HP ALM or Rally.
Score 3 out of 10
Vetted Review
Verified User
Incentivized
It’s being used all across our organization. It addresses IT related issues and is a direct line to assist all workers.
  • They return your calls (usually)
  • Creates helpdesk tickets per issue
  • They usually follow up
  • Can connect to users using interface easily
  • Software tracks specific IT support person assisting customer
  • They don’t always know the real issue and spend too much time figuring out the wrong solution
  • Sometimes they pass around the issue for days.
  • They need to understand all software programs well.
  • Multiple attempts needed to bypass admin access
If the issue is just a question about turning on a feature or setting, JIRA isn’t the best. If it’s a real issue they usually investigate it further and find out.
February 13, 2018

Jira Review

Jesse Brand | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
My organization (about 45 people) is currently either using Jira or is considering the use of Jira to manage tasks and keep a record of past, present, and current projects. Jira provides us a means to better monitor our work, ensuring something is not forgotten. With Jira, it is easy for us as a team to see what each person is working on, the priority of tasks, how many of a certain we have completed, who completed what tasks and how many, and much more. Additionally, the dashboard feature of Jira creates easy reporting, allowing me to condense my work into a manner that my manager and director can use to share accomplishments of the team.
  • Task Management - Keep Track of Tasks
  • Priority Management - Prioritize Tasks
  • Reporting - Create Reports That YOU Need
  • Customization - Better customization for specific needs
  • Ease of Access - More training or helpful tips within the program
If are in a situation where you have multiple tasks that need to be addressed, Jira can provide a means to track and prioritize those tasks. Get rid of jotting notes on paper or sticky notes. With Jira, it's very easy to track what work needs to be done and reflect on work that has been completed.
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Our product team uses JIRA to communicate with developers and manage sprints using the Sprint boards. The commercial support team also uses the help desk feature and other tech teams use Kanban boards to manager their work. JIRA helps our teams stay organized and provides visibility to the work that needs to be done. It is an effective solution and provides a platform for easy communication and collaboration across teams.
  • Organization and prioritization of work
  • The ability to customize (forms, workflows, etc.)
  • The ability to share information easily (adding attachments, adding "watchers" to issues, as well as integrations with other products)
  • The ability to share workflows across projects gets really messy when you want to change one but not the other. You can end up messing up other people's boards without realizing it. It really requires someone who is familiar with the rules of the software to manage things like this.
  • Board configuration is a bit confusing as someone can be an admin on a board but if they do not own the board filter they can not share the board with new people. Visibility to a board is based on the board's filter shares which is just confusing.
  • It would be nice to have more flexibility with workflows. Often times our product managers ask me if they can add a step in their team's workflow and I have to say no because it would affect everyone else who is in the project. I'm not sure why we didn't decide to give each PM their own project... it might be due to their pricing model.
It is really good for product management and organizing day-to-day tasks. I can't really think of anything that it isn't good for. It's a really flexible tool.
Sandip More | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Currently, our Product team, development teams, QA & Customer support teams are using JIRA to manage Development, Production defects, Release cycles. We are using the online version of JIRA with workflow plugins. Workflows have helped us design the development life cycle for various projects as per requirement and helped us to bring efficiency into the whole process. We are using Jira dashboards which are used to run Agile scrum meetings and run weekly/monthly rhythms.
  • It helps in Release Management in our rapid release cycles. sync with Product Management tool and Customer support tools.
  • Supports various kind Of Agile models like scrum & Kanban
  • User accesses, custom story types, Workflow support to automate development cycle.
  • I think they can improve on reporting capabilities to get more insights about developer productivity.
  • Documentation attached to each story is not readable for non-developer teams. If features were better readable UI/UX for business users will help to get all stakeholders in product process to start using JIRA
I don't have experience of working with Larger teams but for a scrum team of size 5-10 it's good.
Mitchell Brand | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
JIRA is currently being used across our marketing department. We use it for task management activities as well as tracking time used for particular tasks, this will then be used to develop proper workflow procedures and timeline expectations amongst the marketing department and interactions with other departments. The goal is to have JIRA put in place throughout the entire organization once we have a large base of advanced users to create the instances for Sales, Operations, etc.
  • Tracking of current projects for large teams
  • Time management
  • Data gathering for developing workflow procedures and expectations
  • Sorting of attachments in individual tickets
JIRA is a perfect fit for any organization where they have a large "in-flow" of projects, tasks, requests, etc. It helps to visualize who and where the majority of the projects are and how much time is being allotted or can be allotted to a particular task. It is particularly helpful in making sure that each team member is given an equal amount of work (if that is the goal) and seeing where each project stands.
December 28, 2017

Great for what we need

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use JIRA to track defects, and the resolution of those defects, across hardware and software platforms. 95% of the engineering organization uses it in one way or another, although the use cases differ.

We use it to track all defect discovery, investigation, implementation and retest. We also use it as a way to facilitate discussion of the defects, and determine priority and resource assignment across the organization.

Furthermore, its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives is a great tool to keep our engineers focused on solving defects, and letting the tool handle the reporting side of things.
  • Its ability to generate reports and dashboards that are accessible, usable and understandable to C-Suite executives
  • Its ability to integrate with other tools through the use of plugins and add-ons (including source code repositories, a big one for use)
  • Its ease of use - new hires don't generally need to be trained at all, they pick up the right way to use the tool within their first week
  • Some reporting needs the ability to be more customized. For certain reports, we still have to export data to Excel...which is a hassle
  • Some features are very software development-centric. We use JIRA to track hardware and software defects, and some of the hardware defect tracking feels shoehorned in
  • The default behavior is to email any user tracking a defect when anything happens. In addition, users get added to the tracking list when they perform any actions on the defect. These two combined means that many users get overloaded with JIRA emails
In a software-centric development environment, especially if COTS source code management is used (Rhodecode, as an example) JIRA shines. We, for example, are able to use it to track defects through implementation down to the specific line of code that changed in order to fix the defect. This means that reviewing how defects were fixed after the fact is very easy.
Fabian Kuhn | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We're using JIRA as a communication and project management tool between our IT and other departments, like management, design, sales and so on. Basically every employee with project management tasks is using it. It helps us a great deal with planning, specifying and tracking the work of our IT department and therefore, the improvement of our online appearance.
  • JIRA is an excellent tool to connect different teams and work styles in an efficient way, without being too specific for some of them.
  • It has a lot of features and settings to offer which really enable you to plan a task in a very detailed way.
  • Thanks to the different conditions of a task, the status can be tracked easily and everyone always knows who's the one who has to provide input.
  • JIRA is not the right tool for people who are looking for an easy, small and quick to learn project management tool.
  • There should be more options to layout a task in terms of tables, image integration et cetera. Currently, the bigger a tasks gets, the more complicated and difficult to understand it looks.
JIRA is perfect for planning and tracking the work of different teams in a company. However, it's a really big tool with a lots of features and therefore, it makes sense to use other project management tools besides it. E.g. we're using JIRA for our IT tasks for which it's suited just perfectly while were using projectplace in the design team which does the job much better in a small team with tasks that are not very complex to specify.
Matt Emge | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use Jira across our whole organization to track one-time and ongoing projects as well as employee time. We use it to track epics, stories, tasks, features, defects and hours spent. We use boards for project workflow and assigning tickets to different team members. We also use it for tracking hours spent on each task according to the client project.
  • It's great for holding all our projects and tickets with teams assigned.
  • It has good features for formatting ticket descriptions and comments for team collaboration.
  • I like the hours tracking feature because it's easy to enter hours for each ticket and also see all my time for the week at a glance.
  • Better formatting options in tickets.
  • Apply UX principles for easier workflow and UI.
  • More options to simplify and cut out unnecessary features that we don't use.
Great for managing a lot of complex projects with a big team where it's important to track time by task. Jira is rich with features for tracking history, power searching, filtering, commenting, assigning to team members, creating custom boards for your own style of workflow and templates for various process styles.
Return to navigation