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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,372
Community Members
 
Community Events
176
Community Groups

How much default workflow's benefit can be literally made use of for admins?

Edited

Hi there,

I am using JSM as an admin. When encountering workflow configurations, Atlassian default workflows should be the first consideration for me. However, the transitions of the JSM default workflow is such a mess. For example, it is hard to tell the difference between Open status and Reopen status. But I suppose it could be useful in some situations. 

Screenshot at Feb 03 12-49-35.png

If this question sounds make sense to you, please let me know how you guys as experienced admins are using those preinstalled workflows if any. 

PS. I am a newbie of JIRA and open to any comments/suggestions about this discussion!

 

Thanks a lot!

Zoey 

1 comment

Welcome to the Community!

This workflow makes perfect sense to me.   Most of my clients are happily using it as a default.

I don't think it is a mess, it's a real-life, simple workflow for handling incoming issues. 

Could you explain why it is "hard to tell the difference between open and reopened"?   Open is the starting state of the issue when it's new.  Reopened means that someone closed it because they thought it was dealt with, but they, or someone else said "nope, it needs more attention".  The difference doesn't matter too much to the end users (people reporting the issue or working on it only really care about "it needs some attention"), but it is very useful for analytics - in an ideal world, you never want to see "reopened" in use, because your agents are fixing everything to the satisfaction of your customers.  People often want to report on re-open, because if you're getting a lot of it, you're obviously not dealing with the issues well enough.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events