You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.