You may unmap the New status from any columns in your board settings.
The new state is used at the time of creation of issue type(say story) and is added in the backlog. The next step is adding estimates and moving the issues in planned state(open state) of the scrum board. If in scrum board I keep two states (New and Open) under Planned status column and suppose next status column is in progress. The transition will happen from New to in progress and not from Open to In progress.
My requirement is transition from Backlog to scrum board with statuses New to open automatically.
I hope this clarifies the situation...
Ok, that's not doable out of the box in a Scrum board.
You could develop your own solution by making calls to the JIRA API, or possibly by using an addon like ScriptRunner for automating that action for you.
Kanban's backlog works like you would like it to, once the New status is mapped to the backlog, but then it doesn't add the issue to any sprints on drag & dropping it from the backlog to the first status mapped to a column.
Another not perfect workaround would be executing this query in the Issue Navigator:
Sprint in (openSprints(), futureSprints()) AND status = New
and perform a bulk-change operation to move all of them to transition all returned issues at once from New to Open.
If you save that query into a filter, you can easily repeat this process in a quicker manner.
Hope it helps.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs