Jira

Excellent, perfect and intuitive

Pros:

Before using Jira, I found it difficult to keep my team's tasks organized in a neat and visually friendly way. In addition, it provides me with many tools that help create a more productive and efficient team, and generates reports that show if the team is making real progress.

Cons:

I consider that the price can be a barrier to entry when planning whether to decide to purchase the software or not, which can deprive many users of trying this wonderful tool. Also, the support one receives for the product sometimes does not solve the problems one may have while using the software.

Best-in-class and Reliable Project Management Companion

Comments: Jira is presently utilized to manage our projects and workflows. We utilize it to manage team members' progress on projects, track outstanding work, and offer context for objectives and procedures. This is utilized across the organization and provides visibility for a large portion of the development effort on a range of projects.

Pros:

1) Integrate seamlessly with development tools like Slack, Github, or Bitbucket. 2) Workspace is very configurable; you may customize the components of each task on your board, as well as create your own icons, labels, and automated processes. 3) Connect all issues/tasks to Epics and view the anticipated outcomes in the Product Roadmap. 4) It offers the flexibility of a kanban board, which provides the user with a clearer view of what has been accomplished, what is in process, and what remains. 5) User story statuses may be used to monitor progress and control workflows. 6) Allows for bulk import of epics and user stories, which speeds up administrative duties if this information was previously recorded in another format, such as CSV.

Cons:

1) Only internal users may be allocated to tasks and user stories. This might result in unnecessarily long delays when external users want immediate input or participation. 2) When many boards exist within a project, statuses (user stories) cannot be established explicitly for each board. 3) User stories may be assigned to just two categories of users: assignees and reporters. JIRA does not permit the assignment of numerous assignees to a single user story.

Jira is good enough, but definitely needs more improvements

Comments: 2 out of 5 stars. In fact, we're (my company) is moving from Jira to Monday.com. It might be a little more, but the trade-off is definitely worth it.

Pros:

Well, the basics. Assignments, delegations and being able to reply to the assigner and to the client him/herself.

Cons:

I'm a UX/UI Designer. So, the workflow is convoluted. The interface needs proper blockings because there are so much thing happening on the main page. Take a look at Monday.com for comparison.

Excellent solution as “One stop shop” in IT industry

Comments: Jira is life savior for many new scrum masters and managers for cost effective project management

Pros:

This software is very easy to manage day to day work,progress,assignments and forcast for different phases of projects..It turned out to be very effective tool in order to achieve efficient and cost efffective operational model in enterprise organizations

Cons:

This software should have most reporting widgets and open integration ports so that various data connectors can be integrated for limitless reporting

Jira can help you tremendously if user the "right" way, or you can shoot yourself in the foot

Comments: I really like it, as I can configure it to suit my needs, I'm constantly reviewing the testing process in our company, making changes to the workflow, adding custom fields, etc.

Pros:

It's rich in features it offers and it's amazingly configurable, two organizations can have Jira installations that are nothing alike!

Cons:

It's not a big issue for me, but I think they should offer more best practices in terms of templates for less experienced users to save them from headaches - they are already taking steps in this direction. Since it's a very large product there are some inconsistencies, doing the same thing in two different parts of Jira can feel like a very different experience.