Jira Work Management vs. Service Autopilot

Jira Work Management suits projects involving multiple teams, such as product development. In our case, the design, development, and QA teams use Jira to track tasks from ideation to deployment. Custom workflows and real-time updates ensure that all teams are on the same page, and the ability to link related tasks helps manage dependencies effectively.

Incentivized

Service AutoPilot is a fantastic system for client service tracking and scheduling. While there are a few features and details I would personally like to see changed or added, the ultimate purpose of the system is well executed, fairly simple to use, and easy to understand. My recommendation would be to add more specific details such as canceled or closed clients and closed/canceled service history on active clients to remain permanently.

Incentivized

• Provide a roadmap of all epics
• Provide a backlog in which you can see all the possible work to be done to create your sprint plan
• Have all our projects within reach
• Have a dashboard with editable columns to manage your work
• Be able to filter by person
• Be able to see past sprints

• service history, tracking
• service scheduling
• service/client notes

Incentivized

• More clarification on where to find useful tools and resources for new users.
• Breakdown of Projects, Tasks, Sub-tasks, bugs is hard to follow and cannot be changed once created.
• The ability to customize the dashboard/home page to fit the needs of individuals could use some work.

Incentivized

• when closing/canceling a service completely from a clients account it would be nice to still have the history to see what they had done in the past incase they change their mind later and wish to continue the service
• cancel/closed client historys would also be nice as if someone sold their home, it would be nice to be able to see what was done on that property prior to inform new owners, etc.

Incentivized

Service Autopilot has a versatile set of features that we use across all facets of our business. We use it for history tracking on clients properties, notes specific to the service and/or the client, as well as pricing details

Incentivized

As we are Atlassian users overall, this entire ecosystem is truly built from a 360 perspective. It becomes the one source of truth, and we can easily see where we are in our projects and where to emphasize focus in the upcoming period. There are some areas for minor improvements, but they are more a matter of preference rather than business necessity

Incentivized

The evolution of Jira Service Desk to Jira work management is accompanied by lot of new features like the List View which allows inline editing, easy column management, the Calendar View bases on extensible modal and state categories, the Timeline View supports tasks and subtasks, the Boards which allow the categorization of status and allow the visibility of subtasks on the cards, Forms can be created very easily, Project templates can be used based on the business area.

Incentivized

We use the two systems collaboratively. Both systems offer different features which we use bits and pieces of what we need from each to make the system work for our needs.

Incentivized

• For our marketing team, Jira Work Management caused us to lose valuable work time due to manual updates that could have been automated.
• Due to lack of creative review tools within Jira Work Management, our team had to pursue other tools that do not integrate with Jira Work Management, thus creating additional OpEx.

Incentivized