Jira subtask lifecycle

[Jim Strange]

Hi,

By default Jira puts all its issue types through the same lifecycle. So a User Story might have Ready->In Progress->Ready for QA->In QA->Done, say. However all subtasks also then follow this lifecycle.

The problem is that subtasks do not have the same lifecycle as user stories. It makes no sense to say that a subtask is "Ready for QA," or even "In QA" - the subtask IS to QA the User Story (in this example)

How do I set Jira up so that a subtask has To do->In Progress->Done lifecycle while the User Story has a different lifecycle?

[Nic Brough -Adaptavist-]

Find, or create, a new workflow that represents what you want to do with the sub-task types.

Go to the list of "workflow schemes" and find the one in use for the project you want to change and check if it's going to upset other projects if you change it.  If it is, then copy it and associate the copy with your project.  If it's not going to affect others, or you want them to be affected, then just work with the existing one.

Finally, go into the workflow scheme and add a line to it saying "sub task: use new workflow".  It may ask you for migration information (if existing issues have a status that is not in the new flow)