Overview
What is Jira Software?
JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the…
Best-in-class project management & coordination, & planning technology
Atlassian Architect
Essential software for a project development
TrustRadius Insights
My Verdict on Jira Software : Should you use it or not!
best for tracking everything
Extremely good on workflow monitoring and handy reporting tools
Jira - The Saviour of lazy people
Streamlining Project Management with Jira: A Quick Review of its Features and Capabilities
Jira Software - Agility with the simplest and most effective #1 ALM solution
Jira Software is capable of end to end product management
Hey guys! let's have an amazing review for this software.
- Problems addressed by this software:
1. Keeping the whole team in single …
Jira - Excellent Project & Workflow management tool
Amazing project manager tool!
Jira helps me do my job better and easier!
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
Pricing
Standard
$7
Premium
$14
Free
Free
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Starting price (does not include set up fee)
- $10 per month
Product Demos
JIRA Project Management Tutorial for Beginners (2022)
The full overview: Roadmaps in Jira Software
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is Jira Software?
Jira Software is a software development tool 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 from a single tool, helping teams release higher quality software, faster.
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.
With Jira Software, teams are able to:
- Track versions, features, and progress at a glance
- Easily 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 Software Integrations
Jira Software Competitors
Jira Software Technical Details
Deployment Types | On-premise, Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Windows, Mac |
Mobile Application | Apple iOS, Android |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(3250)Community Insights
- Pros
- Cons
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
(1-5 of 5)My Verdict on Jira Software : Should you use it or not!
- Ticket management
- Defect management
- Business process management
- Effective communication between cross functional teams
- Easy to use
- Project management
- Interactive UI
- Could be a room for improvement towards documents upload and tracking
- More info of the linked ticket
- Could have better UI
- Load time could be enhanced
- Sometimes document upload fails
Where the team size is big and volume of tickets more.
It is less appropriate we are the team size is less and and the ticket could be solved by an excel sheet itself because there is a cost involved as well as it is not free
- Process workflow
- Team collaboration
- Effective Agile and Scrum management tool
- Effective tool for issue management
- Difficult to track project progress
- Enhanced team collaboration
- Provides custom workflow for the freshers to understand the QA flow
- Difficult for non techy people
- Rally
- Task management
- Issue management
- Team collaboration
- Track project progress
- Customize
- Educate non techy person
- Very customizable, workflows can be defined based on company definitions.
- Improves communication and access to information. It is easy to understand each item's status, priority, and responsible person.
- Allows us to prioritize tasks and estimate delivery dates.
- May have too many options for small and simple projects, making it a little hard to use for starter users.
- It is more expensive that other options.
- Help does not cover all options.
- Integration with other tools (Confluence, etc.).
- Ability to customize and configure workflows and rules.
- Easy filtering options.
- Adaptable to most frequent used agile methodologies.
- Unified development and support tasks in a single tool.
- Collaboration between teams.
- Quicker response times and better visibility of tasks status.
- Trello and Rally Software (formerly CA Agile Central)
- Manage workload
- Prioritize tasks and resource assignment.
- Reduce delivery time.
- Advanced search
- Stories creation
- Time tracking
- Attaching big files
JIRA - Love at First Site for Developers, a Slow Courtship for Business
- Differentiated workflows. It was important to us that new product development could be handled differently than IT implementation bugs, etc., and JIRA does a great job of allowing us to treat efforts appropriately without a lot of complicating customization.
- Card view. The layout of the work items on the board is user friendly and easily gives the team a handle on what is happening during the working period. The drag and drop functionality is constantly lauded by our teams and whenever alternate tools are reviewed, is one of the top features used for comparison.
- Simplified Querying. One of the biggest selling points to the business groups that have taken on JIRA is that finding items in the system doesn't depend on someone with say, SQL talents. Though there are complaints on querying more complicated information from some, overall the WYSIWYG interface for querying tickets is very helpful for business users to "self-service" information.
- Integration with wiki tool (Confluence). This I think is one of the biggest draws for us on the business side. We find that JIRA is sometimes too complicated for the business user and were able to build dashboards and pages that help the business users navigate to what they need to know. Being able to maintain up-to-date reporting from JIRA without having to constantly update is beyond valuable.
- Reporting. JIRA has always been a little finicky on the reporting side in my opinion. The gadgets are helpful but can be confusing if you aren't shown how to use them. Time tracking continues to get worse rather than better with the removal of the one built-in timesheet we had replaced by a paid plugin with fewer options.
- Roles Based Permissions. JIRA is really light on this but you can work it out using validations in the workflows and permission schemes. I think this is not intuitive for most admins and they wind up with a very unrestricted instance of the tool. Sometimes setup can be a pain because of the openness.
- Ramp up is long. JIRA is really difficult to understand and to be properly configured if it doesn’t suit you out of the box. Once you understand all the ins and outs of the setup process you can wind up with a decent tool but it's the fact that you need someone to sit there and learn it before you can use it - not a coherent message to management when pitching Agile.
- Or to some "missing features". Some features that the community feels should be a part of the core product are only available via plugin. Again, the message to management when trying to purchase these is disconcerting to leaders that are used to the "big box, all in one, everything you need, one price" solutions.
- Business Features. Depending on your final configuration you may find tracking business features rather onerous. Based on release structure we have a non-traditional setup where our business projects exist in one space with children work in software spaces. It is the easiest solution to our technical release issues. There is only one ticket type that can have children spanning projects and it is the Epic. Pulling in children tickets is time-consuming and laborious. I discovered that I could automate update of a ticket field on children tickets to help tracking back but it's not elegant and is open to creating gaps should things change (and they often do in Cloud JIRA).
- Positive: this tool provides a convenient and efficient workspace for our developers/QAs as well as transparency for our leaders in the Dev/QA space. Higher level tracking (at the Epic) level gives greater transparency at the business feature level but could be improved.
- Negative: this tool requires a lot of time to learn and maintain. Updates are not always clear in their impact so you do accept (even in a Cloud situation) that if you do not use JIRA with no modifications (I have never heard of this by the way) you will need someone to keep an eye on it. Consider it to be 25% to 50% of a headcount based on your configuration complexity.
- ServiceNow and Workfront
- Prioritization for Stories, etc is very nimble; caveat for the issuetype "Epic" which is decidedly less so.
- Sprint planning
- WYSIWYG query tool
- Dashboard gadgets for Agile development tracking
- Feature prioritization (at the Epic level for our shop) is very hard to use in the Backlog - we've developed a hack where we prioritize Epics in a Kanban board but it's got an element of disconnect to the Backlog planning that isn't very "agile"
- Portfolio tracking - you might try to arrange features according to Business Goals but you'd have to 1) purchase the Portfolio tool from Atlassian which is the same price as the JIRA Software itself or 2) build and maintain insane filters
- Time tracking - your time tracking will again be a choice between purchasing a plugin that does half of what you want or maintaining JQL that does backflips for the same level of value
I'm a fan!
- The biggest impact from experience with JIRA is the transformation it took from when I first started using it, until now. It seemed like the good folks at JIRA really practiced what they preached and I reaped the benefits. When I first started using the agile boards, it was at a time when they had just come out with a new version if you will and were sunsetting the old version (I can't remember the names). Anyhow, the agile board worked enough for me to check the box that I had a backlog. It did the basics. As time went on however, I was thoroughly impressed at the features that they added. It was as if they had been sitting at my desk alongside me and noticing my frustrations and then fixing them.
- Other favorite features, dashboards, saved searches, workflow, labels, advanced search query, linked issues, follow issue, history, batch updates, view in issue navigator. All these features seriously make life easier when working in JIRA. The administrative headaches of product management are out the window.
- I also dig the administrative features like find my field. This makes it so easy for an administrator to identify the cause of a configuration error and fix/test quickly.
- One thing that ever bothered me about JIRA was the rank feature. It used to be a global rank, so I could I query issues and display them in results by order of priority (rank) regardless of what sprint they were in. Now rank is only applicable in the context of a sprint, which is not so powerful really if I want to prioritize across several teams regardless of sprint.
- It would be nice to batch update labels, and not have the "all or nothing" approach. At least they have keyboard shortcuts that make updating many issues one at a time a total breeze.
- At my new company, I'm having a hard time converting my peers and management into JIRA admirers. Their concerns are mainly the price and the ease in which the system can be integrated into our homegrown system. Can you make some sort of browser plugin that could compare how long it takes me to complete the same work in JIRA vs my current application?
- As a product manager I needed to make sure that all teams were aware of priority and that new items went through triage and were accounted for in a timely manner. JIRA took us away from the headache of spreadsheets and daily meetings, to one transparent system with real time dashboards that required no meetings. People could just do their work because they knew what was the next most important item. This must have saved hundreds of thousands of hours over the years.
- keyboard shortcuts are amazing and same so much time
- Find my field is an amazing feature that also takes me to the correct admin config for me to make the updates I want so that I don't have to hunt around for what I'm looking for.
- The advanced search and saved searches make finding the issues important to me very easy. Nothing falls through the cracks.
- Managing labels across the system can be tough. It can get ugly if you have a lot of people using them and one person uses a capitol and someone doesn't. Then your searches need to include all permutations of the label to make sure you get the results of issues you're looking for.
- Configuration can be a bit daunting, but the Atlassian university was a great help.
Atlassian JIRA
- Easy to use and configure.
- Provides visibility of workloads.
- Provides visibility and tracking of progress against certain tasks.
- Allows you to go back and track historical decisions.
- Good roadmap, existing and new features always being worked on.
- Within the Agile area it would be nice to be able to track versions more easily, whilst it does it I don't find this area all that intuitive.
- From an IT perspective this allows us to make sure we are managing workloads and due dates effectively.
- From an organisational perspective it provides us with a tool we can use to track issues and tasks, with minimal setup overheads and minimal training. It is also very configurable, allowing us to configure JIRA to match business processes rather than needing to change business processes to match JIRA.
- Adding new issues
- Tracking progress and recording comments against an issue
- Assigning issues to employees so they are responsible