I am looking for a way to achieve the following for stories & task issue workflows:
The problem I am having is that if I set the first status in the workflow to "To Do" then the items from the roadmap go straight into the backlog, overloading it with stories and making it hard to know what is ready to be worked on or not. If instead I set it to "Needs Requirements" then if we need to break down a story in the backlog in sprint planning and add a new story, it disappears from the Backlog and you have to go find it in the "Issues" list and update the status to move it into the Backlog.
I've looked at the automations but I can't see any way of automatically updating the status based on which window the user is entering the data.
Is there a way to do this, or an alternative workflow I should be considering?
Hi @David Moore , welcome to the Community!
The short answer is no, there is not a way to have an issue of a specific type be created in a particular status depending on which application/view it's raised in. The issues would either need to:
If the difference between these two views is that you create standalone/orphaned issues in your backlog view but create issues as a child of an existing Epic in your roadmap view, then you could do something like the following:
When issue created
If type = X
If issue has no parent
Then transition issue to status Y
Which would allow issues created with no parent to automatically shift from Needs Requirements into To Do.