Jira Software Reviews

“Workflow flexibility and design”

Pros

Right away, the platform feels well put together and the interface is simple enough that almost anyone can start working with it without much trouble. It's also very flexible and the customization options can be tailored to match specific project needs. Another big plus is that issue types and workflows can be created differently from one project to another which makes it very adaptable.

Cons

Test case management and execution still have room for improvement. Also, when it comes to deeper customization, trained people are really needed to design and set things up properly.

“Helpful task tracking”

Pros

Managing and organizing work is really helpful with this especially when you're working with larger teams. It lets you track and review the time spent on each task and the connection with Git projects is a big plus since you can also see the commits related to each task.

Cons

At times it can be quite slow and on some dashboards not all of the available options are visible.

“Excellent ticket visibility”

Pros

One thing I appreciate most about this tool is how well it interacts with users when creating incident and request tickets, tracking the time spent on activities and showing the full workflow for each ticket.

Cons

At the moment, I haven't come across anything negative during the time I've been using this tool.

“Adaptable workflow setup”

Pros

Very customizable overall. It supports multiple methodologies so you can configure it to match the way your team prefers to work.

Cons

It can feel a bit heavy or slow at times while using the app. Report generation also takes more effort than it really should.

“Developer-friendly platform”

Pros

Right from the start, this software feels very user-friendly while still being extremely capable. Every entry can be organized into practically every relevant subsection a developer might need which makes tracking work much more structured. It also lets you document the fix along with the related source code which adds a lot of value. Overall, it's the kind of tool both managers and developers would genuinely enjoy using.

Cons

Honestly, I can't think of anything disappointing about this software.

“Daily task companion”

Pros

It's part of my daily routine and I use it to create and manage a lot of tasks throughout the day.

Cons

I'd still like to see more features for labeling tasks and improving sorting options.

“convenient integrations and kanban”

Pros

Working with the integrations across other platforms like Git, Bitbucket and Slack has really made the workflow much simpler. Everything stays connected so each ticket can be linked to the tools you're already using to work on it. The drag-and-drop functionality on the IT board is also very polished and fluid which makes managing tasks much more convenient.

Cons

Creating a new release and managing older releases could be improved.

“Useful ticket visibility but steep learning curve”

Pros

One thing this tool does really well is keeping the workflow organized. It has separate status sections for ongoing work, tasks that still need to be done and items that are already completed which makes it much easier to understand where everything stands. Ticket management is one of its strongest features. Another function I really appreciate is the ability to control who can view specific issues since security levels can be assigned based on the user. I also see it as a very valuable product for teams following agile methodology because it makes project management more manageable. Overall, the transparency it provides helps users clearly understand what is happening across the project.

Cons

Getting started was a bit confusing so I would not call it very beginner-friendly. When I first began using it, a few things were not that easy to understand. Other than that initial learning curve, I have not really run into any major problems.

“Custom dashboards that deliver”

Pros

Our team relied on it for project management and the standout benefit was how much each user could customize their dashboard. That flexibility made a real difference in day-to-day work because everyone could set up the tool in a way that matched how they actually used it.

Cons

For the kind of project management we handle especially since it is not centered around bug tracking, the platform felt overly awkward and more complicated than it needed to be. If the goal is a collaborative team space for managing projects, this would not be my recommendation.

“Helpful dashboards and builds”

Pros

Dashboard makes it simple to keep up with the status of any work item. It's also very useful for spotting major and critical blockers quickly and I can monitor the build status of deployments without much effort.

Cons

Mobile version of the application still needs some improvement.

“Excellent for remote teams”

Pros

Working with remote web developers is much more organized with this software. It's been really helpful for our team to monitor incoming projects, stay updated on their status and assign tasks clearly. We also use a point system for each project based on how complex the work is which helps a lot with planning.

Cons

Since I was just getting started with it, I needed a bit of time to figure out how everything worked especially because I had been using Basecamp before.

“Team project toolkit”

Pros

Right away, this handled complex projects and supported our medium-sized team without causing any problems. The toolkit feels very complete for managing sprints, tickets, project progress and user-specific tasks. Being able to customize the data fields and choose what information to display was also a big plus.

Cons

Setting up the ticket workflow was a bit challenging at first and it took us some time to figure out the right process. Once everything was configured properly though, it worked really well.

“Customizable and integration-ready”

Pros

Flexibility stands out, you can shape it to fit almost any use case and customize it extensively. The built-in integrations are also a strong starting point since they work immediately at a basic level without much effort.

Cons

One downside is the leaky abstraction, things that seem project-specific are actually global so changes that look local can end up affecting everyone in a very disruptive way. Power users tend to run into this mistake again and again. Its high level of customization can also encourage people to use it for things it's not really meant for, like building out business workflows when a separate tool would be a better fit. On top of that, the basic integrations are useful at first but are often outgrown pretty quickly and more established organizations may find other tools better suited to their needs.

“Flexible workflow fields”

Pros

The customized fields really help tailor the system to the specific needs of your business which makes it much more adaptable for different workflows.

Cons

It can feel like more than a smaller business needs especially when handling a low volume of tickets.

“Agile sprint planning”

Pros

Built with agile development teams in mind, this works really well for sprint planning. It helps organize work clearly by breaking tickets down into epics, stories, tasks, bugs and similar items which makes planning much more manageable.

Cons

Since the redesign, a few features have felt missing or harder to find which can be frustrating at times. I'd also really like a better way to view all assigned tasks together in one dashboard.

“Cross-team issue support”

Pros

It works well for keeping track of issues and sharing updates across teams as well as between different companies.

Cons

One thing that could be better is how every update goes out to all watchers and reviewers on an issue. It would be much more useful to have the option to mark certain discussions or updates as internal only.

“Complete SDLC suite”

Pros

One of the best parts of this software is that it offers a full package for managing the SDLC and it also integrates really well with supporting tools used to handle the STLC.

Cons

Feature I'm not happy with is the editing feature in Confluence.

“Agile transparency done right”

Pros

If your team talks a lot about Agile, this is the kind of tool you should actually be using. Pretty much every successful company I've seen with a strong engineering side relied on something like this. It makes product development much easier to manage, keeps workflows organized and brings a lot of transparency to the process. Multiple people across the company can follow along with engineering work, whether that's building new features or troubleshooting problems.

Cons

The biggest downside is the cost. A lighter or more affordable license option would make a big difference especially for smaller companies that could benefit from it but may not be able to justify the full price.

“Tracking and agile visibility”

Pros

Keeping tabs on tasks and bug status is much more organized with this tool. It lets the team manage project-related details through simple drag-and-drop actions which makes updates much faster. I also appreciate the visibility into project, sprint and task progress, along with the filtering options and reporting features for checking overall status. Another big plus is that it supports multiple workflows such as Kanban and Scrum.

Cons

One downside is that the system is extremely detailed so the full ticket lifecycle from opening to closing can feel overly heavy especially for very small tasks. It also feels too complex for smaller projects and the user interface can be difficult to navigate at times.

“Kanban with confluence”

Pros

It works really well for easy Agile story and ticket management. The Kanban board is great and being able to customize the ticket flow adds a lot of flexibility to how teams work. The Confluence integration is also a big plus and fits nicely into the overall workflow.

Cons

Sub-ticketing setup still needs improvement since parent tickets can be marked complete before the sub-tickets are finished which makes items easier to lose track of. Reporting around utilization is also pretty limited. On top of that, addon licensing can get expensive and it's difficult to present multiple concurrent projects under one shared backlog.