Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Team collaborated project remove to do have created items go to backlog instead

Erica Grant October 19, 2021

I seem to be unable to remove the 'to do' column from my kanban board on a team collaborated project. I'm the admin on this board and ideally new I would like all newly created tickets to be set to go to the backlog. If I remove to do and have a backlog all the newly created tickets go to 'selected for development' or somewhere else on the start of the workflow. I want a place to park tickets until we decide as a development team to pick them up. Here is a picture of the current work flow I'm trying to change: 

workflow.jpg

1 answer

1 accepted

1 vote
Answer accepted
Walter Buggenhout
Community Champion
October 19, 2021

Hi @Erica Grant,

As far as I know, in team managed projects all statuses must be mapped to a column of your board and the first column of your workflow should be the left-most column on the board.

If you activate the backlog feature, you will indeed see the behaviour you describe. The first status of your workflow will be represented in the backlog view AND as the first column of your board. Which means your to do status will be on the board and require your users to take an additional step to move prioritised issues to selected for development.

Kanban boards in company managed projects. There you see the behaviour you would like to see, as you do map your first status to the backlog column of the board, as you can see in this example:

Screenshot 2021-10-20 at 07.33.18.png

Another workaround, that would require a different way of working, would be to use sprints and eliminate either the to do or selected status from your workflow. The process of elaborating issues first, adding them to a sprint when ready and then starting the sprint then helps facilitate the handover to development.

In reality, we often see people use a more extensive workflow for stories with an elaboration/analysis part first and a handover to development next. That can be managed with different boards (e.g. kanban for the elaboration and scrum for development), but you would need to switch to company managed projects for that. In team managed projects you cannot leave statuses unmapped from a board.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events