Forums

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

Breaking up a checklist

Joey April 27, 2020

I have a 3 phase process with about 7 tasks each.  looking for some help in how to set this up with checklists.

My initial thought was to have phase 1, 2, and 3 as statuses in the workflow and move a story through that.  the problem was the length of the checklist.  QUESTION is there a way to replace a checklist with a different one upon transition?  id like to avoid having a massive checklist with all tasks' items in it if possible

instead of having the statuses = phases, I could simply use to do, in progress, done for the statuses and have a story for each phase but then i'd lose the ability to query on the status.  

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 28, 2020

Hello @Joey

Thank you for reaching out.

Per your description, I understand you want to break down your process into multiple hierarchies, where your issues would have 3 phases with 7 tasks on each phase. Is that correct?

Analyzing the scenario you are trying to achieve, I believe the use of Epics and Sub-tasks issue types would be the best way to organize and make sure all the details for each phase and task of your process will be correctly documented. Allow me to explain it better:

Jira have three default hierarchical levels for issues:

Epics --- Standard issue types (Stories, tasks, bugs, etc) --- Sub-tasks

  1. Epics are used to map a large amount of work, so you could use them to address the whole process you have and where the phases will be planned.
  2. Stories/Tasks can be used as the Phases that the process will have, linking three stories (Phases) for each Epic
  3. Sub-tasks would be used to map the 7 tasks that should be done in each of the phases (Story)

Doing the steps above, you will be able to configure three issue types linked to each other with a clear hierarchical structure to map your whole process details, properly covering all the topics you need on each of them and being able to query any information you need.

That being said, I would like to ask you for more details about the following sentence:

instead of having the statuses = phases, I could simply use to do, in progress, done for the statuses and have a story for each phase but then i'd lose the ability to query on the status.  

Statuses and issue links can be returned in a Jira JQL query with no problem, so I would like to better understand your goal if this solution is not applicable to you.

Additionally, you can check the documentation below for more details on how you can configure Epics and Sub-tasks:

What is an epic? 

Configuring sub-tasks 

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5
TAGS
AUG Leaders

Atlassian Community Events