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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I would like to know if it's possible to create an automation rule so that when I create issues, they would automatically appear in the 'To Do' workflow status (first workflow step) rather than the requirement to move each task from the backlog.
Is this possible? Would appreciate any advice on this.
Thank you,
See
But ... if this has to be done always ... maybe you should check the workflow and wee if you can't use one without a backlog status
Hello @tessa
Welcome to the Atlassian community!
Are you working with a Team Managed project or a Company Managed project? That information will show at the bottom of the navigation panel on the left.
Are you working with a Scrum board or a Kanban board?
If you are working with a Kanban board, and you always want the issues to appear in the first column of the board, you can simply disable the Backlog screen. Then all issues will automatically display on the board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @tessa , welcome to the community and thanks for your question.
You could create an automation with the trigger for when the issue is created and then use an action to transition it to the status you want.
You could also just modify the workflow and then the board column mappings if you don't want to use the status of backlog. It depends on what you would prefer. If you never want to use the backlog status, I would say you can just get rid of it and then you don't need to have an automation running in the background.
If you have some issue types that need to still use the backlog, you could use an automation, as you suggested.
If you need help setting it up, please write back and give us your feedback. Someone will be glad to help.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.