Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Change default JSM service request workflow and allow step from Waiting for Customer to In Progress

Please advise the pros and cons to change the default workflow for JSM service request.  So an issue can be transitioned to In Progress from Waiting for Customer status directly.

Thanks much!!

1 answer

1 vote
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 26, 2023

It should not affect anything, I have made that change and added other statuses/transitions without any issues. The default setup only have an automation that is dependent on waiting for support and waiting on customer so the status is automatically changed when either an agent or the customer adds a comment.

That is my thought too.  But since JSM defaults it so it makes me wonder if I miss anything.

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 26, 2023

Every project template has a default workflow attached to it, that doesn't mean that you can make changes to it. The only thing you have to consider when doing it is if you have automations that expect certain statuses or if the workflow is shared across multiple projects. Another thing is that you should never rename a status in a workflow, since that status may be used in other workflows. If you need to rename a status, then do that from Settings > Issues > Statuses since that will tell you how many workflows are currently using it.

Like Bin Liang likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events