Status/ Caterogie / Workflows questions (full description project)

[Alan Chêne]

Hello everyone, i have a specific problem about states and categories, here is a full description of my implementation for better view of the problem, lists of question will be in the bottom of the page.

Description:

In my project, i have 1 scrum, and 6 Kanban boards: 

1* Sprint (Scrum)

2* User Story (Kanban)

3* Design (Kanban)

4* Development (Kanban)

5* Bug (Kanban)

6* Epic (Kanban)

The workflow schema turn around the movement of a story into the different boards. So I will describe the next workflows from the 2* board for better understanding.

2* User Story (Kanban)

Filter: show only Stories issues

Backlog: Creating any story .

Statut associated: « Backlog », no column in board

Board Columns:  Business Analysis -> Ready For Design -> Design Doing -> Tech Validation                                                      To Do -> In Dev -> In Test -> Code Review -> Done 

Board Statut:    Business Analysis -> Ready For Design -> Design Doing -> Tech Validation -> « Backlog sprint/Sprint* »-> To Do -> In Dev -> In Test -> Code Review -> Done

Backlog sprint/Sprint*: when an issue goes from « tech validation » to « Backlog Sprint » status, the issue disappear from the board and goes to the backlog of the 1* Sprint (Scrum). When the issue will pass from « backlog sprint» to a real sprint, the issue will go to the « To Do » column on boards 1*, 2*, 4*.

1* Sprint (Scrum)

Filter: show only Bug AND Stories

Backlog: Stories pushed in when transited from "Tech Validation" status to « Backlog Sprint » status available in 2*, 3*, 4* Boards

When i push a Stories or Bug from the Sprint Backlog to a real sprint:

                                    °Boards 1*, 2*and 4* : Issues available in the "To Do" column

Board columns: To Do     In Dev      In Test      Code Review      Done 

Board status:    To Do -> In Dev -> In Test -> Code Review -> Done 

3* Design (Kanban)

Backlog: show stories transitioned from « Business Analysis » to « Ready for design » 

Status associated: « Ready For Design »

Board Column: To Do -> Doing -> Tech Validation -> Done

Board Status : To Do -> Doing -> Tech Validation -> Backlog Sprint 

4* Development (Kanban)

Filter: see only stories and bug

Swimlane : 2 (Stories and Bug separated)

Backlog: No Backlog

Board Column: Tech Validation-> To Do-> In Dev-> In Test-> Code Review-> Done

Board Status:   Tech validation -> Backlog Sprint/Sprint* ->To Do -> In Dev -> In Test -> Code Review -> Done

Backlog sprint/Sprint*: when an issue goes from « tech validation » to « Backlog Sprint » status, the issue disappear from the board and goes to the backlog of the 1* Sprint (Scrum). When the issue will pass from « backlog sprint» to a real sprint, the issue will go to the « To Do » column on boards 1*, 2*, 4*.

5* Bug (Kanban)

Filter: only bug

Backlog: All issue Bug created

Statut associated: Backlog

Board Column: Tech Validation-> To Do-> In Dev-> In Test-> Code Review-> Done 

Board Status:   Tech Validation -> Backlog Sprint/Sprint*-> To Do -> In Dev -> In Test -> Code Review -> Done  

6* Epic (Kanban)

Filter: only epic

Backlog: No Backlog, when created, the epic goes to « to do » column automatically.

Board Column: To Do-> Running -> Doing-> Done 

Automation:

-> When an epic is created in « To Do »,  if one features associated to this epic is done or is in a sprint, the epic goes in « Running »

-> When all the issues associated to an epic are done, the epics transit to « Done » column.

 QUESTIONS :

• Is it possible to create a specific Backlog in a Scrum board to create my « Sprint Backlog » with this specific statut? (there is no column backlog like others kanban boards parameters)
• Is it possible to create a new category to add « Sprint Backlog » as a « To Do » Catégorie, to separate the To Do sprint catégorie to the others to do things (backlog boards things) ?
• How can I manage the automations in the Epic section ? ( 1: When an epic is created in « To Do »,  if one features associated to this epic is done or is in a sprint, the epic goes in « Running » 2:  When all the issues associated to an epic are done, the epics transit to « Done » column.)

[Rudy Holtkamp · Accepted solution]

Hi @Alan Chêne ,

That is what you call an elaborate story! I will focus on your questions:

• Is it possible to create a specific Backlog in a Scrum board to create my « Sprint Backlog » with this specific status? (there is no column backlog like others kanban boards parameters)
  No, in a Scrum board you have a backlog. There you can create (multiple) sprints. You can drag and drop issues to these sprint regardless of their status. That is, the statuses need to be in the JQL of your board filter. Only the issues from the sprint that you started will show up on the board.
  You could add a sprint as a kind of collection of issues. We have occasions where we store issues in such a sprint which need further analysis/clarification before we move them to another sprint.
• Is it possible to create a new category to add « Sprint Backlog » as a « To Do » Catégorie, to separate the To Do sprint catégorie to the others to do things (backlog boards things)?
  No you can't add another category. You can add the never-start-sprint as described in the last part of the previous answer. 
• How can I manage the automations in the Epic section ? (
  1: When an epic is created in « To Do »,  if one features associated to this epic is done or is in a sprint, the epic goes in « Running »
  2:  When all the issues associated to an epic are done, the epics transit to « Done » column.)
  
  First the second requirement: For these automations take a look at the templates that come in the automation section. 
  2. Search for 'When all stories are completed → then close epic' . Use this template it will be ok for you
  
  1. Then go back to the templates and use the same template again. Now you need to change the trigger and change the Related issues condition which is in the branch part of the rule. The condition should be something like
  status = "To do" and sprint in openSprints() 
  You might want to add other statuses too, that is up to you. But the second clause is important, because you only want the Epic to transition if a child is moved to a running sprint. Since you can add a lot of non-running sprints in your backlog.
  
  Below a screen shot of the condition:
  

Good luck