I use Jira for project and task management. It brings accountability and aligns everyone towards the same goal by setting up a target for each employee. I like how it helps with progress tracking and managing the project load. It sets up accountability and assists in prioritizing tasks with defined priority levels, keeping the team focused. Although the initial setup was difficult, it became easy with use, and everything worked well for me. The Overall performance of team gets improved Review collected by and hosted on G2.com.

So far, it has worked well and I don’t have any major issues. That said, it feels like it’s missing stronger AI support. AI features such as effort estimation should have been developed. Review collected by and hosted on G2.com.

What I like most about Jira is how easy it makes it to organize and track my work. As a UI/UX Designer, I can clearly follow design tasks, requirements, progress, and bug tickets in one place, which makes coordination with the development and QA teams much easier.

I especially like Rovo, as it has helped me save a lot of time when finding information, understanding tickets, and working through project-related tasks. Overall, Jira helps me stay organized and gives me better visibility into what the team is working on. Review collected by and hosted on G2.com.

What I dislike about Jira is that it can sometimes feel overly complex for simple tasks. There are many fields, statuses, filters, and configurations, and it can take extra time to find the exact information I need. Another issue is that when there are a lot of tickets and notifications, Jira can feel a bit overwhelming. I think a simpler way to highlight the most important updates, feedback, and blockers would make it easier to use day to day. Review collected by and hosted on G2.com.

Jira gives me the visibility into the status of development work. I can break larger work into tickets, assign ownership, track progress, and see what is still pending without having to rely on separate spreadsheets or messages.

The workflow and issue history are particularly useful. When working on a feature or fixing an issue, I can see the discussion, updates, and status changes in one place. It makes it easier to understand what has been done and what still needs attention, especially when multiple people are involved. Review collected by and hosted on G2.com.

The main thing I dislike about Jira is that it can feel heavy for simple tasks. There are a lot of fields, workflows, statuses, and configuration options, and teams can end up making the process more complicated than necessary.

It can also take some time to find the information I need when a project has a large number of issues. For smaller teams or straightforward work, I sometimes feel that keeping tickets updated can become additional overhead rather than helping the team move faster. Review collected by and hosted on G2.com.

The biggest benefit of Jira for me is that it keeps everyone on the same page. Whether I'm tracking project tasks, managing sprint deliverables, or reviewing defects, everything is available in one place. I no longer have to rely on multiple spreadsheets or status emails to understand where a project stands.

I also like how easy it is to create dashboards, track progress, and monitor team capacity. The ability to customize workflows and automate routine activities has helped our team improve efficiency and focus more on delivery rather than administrative work.

For large projects involving multiple teams, Jira provides the visibility and structure needed to keep work moving smoothly and ensure deadlines are met. Review collected by and hosted on G2.com.

Jira can have a learning curve for new users, and heavily customized projects can sometimes become complex to navigate. I would also appreciate more ready-to-use executive dashboards and reporting options. However, these are minor drawbacks, and the platform's flexibility and project management capabilities make it a valuable tool for managing complex initiatives. Review collected by and hosted on G2.com.

Jira excels at project and issue tracking. Its customizable workflows, Scrum/Kanban boards, and real-time visibility into tasks help teams collaborate effectively, stay organized, and deliver projects on schedule. Review collected by and hosted on G2.com.

Can't create tasks under user stories to capture complete trail of work done with proper efforts only sub-tasks helps for this purpose. So, I find it easy Agile Central Clarity tool. Also, Complex workflows and excessive customization can sometimes make navigation difficult and increase the learning curve. Additionally, performance can occasionally slow down when working with large projects or heavily customized boards Review collected by and hosted on G2.com.

What I like best about Jira is the flexibility it gives us to manage work across the whole development and testing lifecycle. I use it heavily for defect tracking, test and development status, Epics and reporting, and the ability to use JQL to create very specific searches and views is particularly useful. It makes it easy to quickly understand what is ready for testing, what is blocked and where issues sit within a project. I also like how configurable the workflows, dashboards and filters are, as they allow Jira to be adapted to the way different teams actually work rather than forcing everyone into the same process. Review collected by and hosted on G2.com.

The main downside of Jira is that its flexibility can also make it quite complex. There are a lot of configuration options, workflows, custom fields and integrations, so the experience can become cluttered and there is a learning curve for new users. More complex JQL queries and reporting can also take time to get right, particularly when working with Epics and different issue relationships. Performance can occasionally feel slower when dealing with larger searches or dashboards. I’d also like to see more intelligent or AI-assisted features that make building complex queries, reporting and finding the right information easier without needing detailed knowledge of JQL. Better guidance within the product would also help users get more value from its advanced features. Review collected by and hosted on G2.com.

I like Jira’s flexibility, ecosystem connectivity, and deep process control. Custom workflows and issue types let it fit different team processes, and its built-in flow diagrams and burndown charts give me data on team capacity and bottlenecks. No-code automation rules save admin time by moving tickets, assigning owners, and sending alerts. Jira also scales from small teams to large organizations, and its roadmaps link company initiatives to individual developer tasks and show long-term milestones. I like how it connects with tools like GitHub, Bitbucket, and GitLab, and with Confluence, where requirements, meeting notes, and diagrams can be embedded in Jira issues. The Scrum and Kanban templates and default workflows made it straightforward to set up a basic board and start logging issues. Review collected by and hosted on G2.com.

I found the initial setup fairly straightforward, but it was frustrating to fit Jira to my exact team process and it needed ongoing adjustments. The initial learning curve, administrative overhead, and potential UI clutter can make it feel heavy for smaller teams or non-technical departments. Review collected by and hosted on G2.com.

Jira is seamless and well-integrated with Bitbucket. Its dashboard provides a clean and intuitive interface that makes it easy to organise and manage tickets. It also allows me to update ticket statuses according to the defined workflow. The most important aspect I like about Jira is its seamless integration with other applications, which makes the overall development and project management process much more efficient.

It also significantly improves the overall workflow. As a developer, I can easily track my assigned tasks, see which tasks are currently in progress, identify completed or closed tasks, and keep track of what needs to be worked on next. This gives me a clear overview of my work and helps me stay organised and focused. Review collected by and hosted on G2.com.

One thing that can sometimes make Jira a little difficult to use is the comment section. There is an additional formatting option that allows users to make comments stand out by adding colours, headings, and other formatting. However, to use these features, you need to write the comment using Jira’s specific text-formatting syntax. You then have to save the comment and check how it appears, which can sometimes feel inconvenient and less intuitive. Review collected by and hosted on G2.com.

I like how Jira bridges high-level strategy and everyday execution. Its automation rules are especially useful: I can set up trigger-based actions without code, like moving a ticket to ready for testing and assigning it to QA when code is merged. Auto-assignment, SLA tracking, and automatic status changes and notifications cut down on manual updates and help keep the board aligned with what’s happening. I also value Jira Query Language and custom dashboards for specific searches and tailored views, along with development integrations for contextual ticket linking and traceability. Linking branches and commits to Jira issues also updates ticket statuses and shows pull requests and deployments. The scrum and Kanban boards, organized backlogs, parent-child relationships, and sprint planning help me handle larger software projects. I can also get a basic scrum or Kanban setup running in a few minutes, and the initial wizard is fast and straightforward. Review collected by and hosted on G2.com.

I find Jira has a steep learning curve, and its feature-rich interface can feel bloated, rigid, or overwhelming for non-technical users and new team members. I’d like simpler default setups for non-software teams like marketing or HR, without extensive administrative configuration. Review collected by and hosted on G2.com.

Jira is one of the popular task tracking software, and I like Jira for tracking my tasks and managing tasks within the team. The feature that allows tracking the time duration of the open ticket is one of the best features. Also, the AI feature allows me to do my work faster. The UI is also very easy to explain to new users in my team. Some of the features justify their pricing as they offer more advantages. Also, team integration is very easy because team management is very smooth in Jira. When I change the status of the task, it changes instantly on all other users' dashboards, making the performance outstanding. I remember when I had an issue related to my plan, the support team resolved it very fast. Review collected by and hosted on G2.com.

Jira has lots of features, but the issue is some of them are not used by me, yet they still show on my screen, making the Jira dashboard bulky. I recommend adding a setting to turn off the features not used by the user. I want Jira to provide an option to enable or disable features from the UI. Review collected by and hosted on G2.com.