JIRA Service Management

Probably the top program for managing projects

Comments: Jira is a sophisticated and flexible project management solution with a wide range of applications. Jira's strengths lie in the depth of its task management features, the breadth of its integrations, and the depth of its reporting and analytics tools, all of which contribute to the program's capacity to help you better understand your projects and teams.

Pros:

To accommodate the fact that various people have different ways of doing things, this user interface may be easily altered to fit individual needs. Jira makes it simple and quick to design and implement unique workflows and rules. One way to break down large projects into manageable chunks is to keep everyone in the loop on how things are shaping up.

Cons:

Jira's flexibility allows for personalization, but more in-depth modifications may call for specialized skillsets.Performance difficulties: Some users may have performance issues, especially when working with larger projects or those that include complicated procedures.

Excellent service and project management tool

Comments: For the past five years, I've been using Jira, and during that time I've noticed a big improvement just about every time. It has been easy for us to keep track of the work that other teams have completed by logging it and adding service level agreements. You can use it to delegate tasks within your team, track progress on common goals, and share updates with your colleagues in real time or behind closed doors. Because of this, it is an incredible instrument.

Pros:

The default settings for Jira Service Management allow you to maximize its potential right away, with nothing in the way of setup. It is possible to personalize it with a wide variety of settings so that it functions just how one would like it to.

Cons:

Because our SSO implementation needs it, in order for a user to sign into the customer portal, they will first need to sign into the parent Jira site.

Great for Smaller Businesses, not for the Large Enterprise

Pros:

Service Management is very easy to get going "out of the box" for small organizations. We stood this up apart from our enterprise's main service management tool because we had special needs for our intake forms and this allowed us to do the customization needed without going through rigorous development through the enterprise level tool.

Cons:

Form design for your main portal can sometimes be wonky, as navigating through the options takes a bit of getting used to and aren't the most intuitive at first. Workflows are also very simple and complex decision-making based on external data is not readily available.

One of the best choices for a customer service desk

Pros:

Highly customisable service desk portal, from the fields to the UI. We can set up a new portal in minutes for every new project and easily tie the tickets to our internal Jira Software projects keeping internal and external discussions separate.

Cons:

SLA management should be made easier as well as the reporting options. Naturally the easy integration between the service desk and the software issue tracking system occurs if you are using Atlassian, good luck with other tools.

A great tool that brings visibility, productivity and collaboration to the team

Comments: You can take so much value from Jira is used correctly and if the team is well aware on how to use it. We use it on our daily standups and it helps a lot see what other team members are doing and their progress. You can easily spot who has more buffer and who needs a hand. The history feature is also a big plus to see what was changed in the description of the cards. I see this tool is a perfect fit for big companies.

Pros:

Estimating the team's velocity can be pretty accurate when the users fill in their Story Points and the time to completion. Cards also provide a lot of information, team members can collaborate in the comments section and the ability to create sub-tasks is a big plus.

Cons:

Jira can become overwhelming for newcomers, specially if there are no explicit policies on how to use it. Also, when marking tasks as Done, it feels the completion time fields are a bit redundant.