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,466,414
Community Members
 
Community Events
176
Community Groups

How do I modify my workflow to include an additional To Do step for anonymous access requests?

I have a workflow to complete an issue for those users within my group.  I want to add an additional workflow To Do category that applies before the first group To Do category and is only used for issues submitted by anonymous access users.  This To Do step would serve as a queue for work management issues, submitted by anonymous access users and triaged by the users within the group.  After the submitted issue is triaged, the group would move that issue to the first group To Do category.  Issues created by the group would bypass this queue category default into the first group To Do category.

2 answers

1 accepted

0 votes
Answer accepted
John Funk Community Leader May 16, 2022

Hi David,

I don't know if you are still needing help with this or not, but you can have the initial status be called whatever you like and that's where all issues land. 

But then you can have an automation rule that will automatically transition the issue to the next status in the workflow if is approved or from some other criteria. That status can be called whatever you like also - it just has to be a different name than the first status. 

0 votes

I'm afraid there is no way to add a new status category.

Maybe my terminology was poorly chosen.  I do not want to add another option than the default "To Do", "In Progress", Etc.

I simply want one to do option (To Do 1) as a first step for anonymous access users and another to do step (To Do 2) as a first step for registered users.

For anonymous access users, their issues would follow To Do 1, then To Do 2, and so on.  Registered users' issues would begin at To Do 2 and advance from that point.

This scenario allows the registered users to review the anonymous users' requests, completing any fields that were incorrectly filled out or not addressed at all, and advancing the issue to To Do 2.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events