Defect and Sub tasks Management

[Praveen_ Deepak _Synchrony_ consultant_]

Hello All,

Whenever a defect is raised in jira board. we have couple of tasks to be done in multiple sprints . But in jira sub tasks could not be moved to different sprint and they stay where ever parent defect stays. because of this i had to move the defect to multiple sprints which is kind of Spill or in complete work.

Eg: - 

Defect 1 has dev task , QA task. i want to do dev task in sprint 1 and QA task in sprint 2 thus i want to close Defect 1 by sprint 2. 

[Md_ Abrarul Huda]

The best thing you can do here is split the defect into tasks.
I'm guessing for your board, defect is the same level as a task. That's why, you can only tag subtasks. But if you break the main defect down...

1. Simply Breakdown the original defect into achievable goals. And make separate tasks.

2. Link the original defect item as "Split from". 

3. Than you can assign each separate task to a separate sprint.

4. Write an automation rule to auto complete the original defect once all "Split to" items are closed.

Should make life a little easier if you don't want to move the main defect ticket.

[Chris Rogers]

@Praveen_ Deepak _Synchrony_ consultant_ 

A key question for you and your team is: "When can you consider a defect closed?"

It sounds as if you want the Dev Tasks and QA Tasks associated with your Defects closed before the Defect is resolved.  If so, then what you have working now meets that; the Dev Task and QA  Task aren't complete, so the Defect isn't complete and should be moved to the next sprint.

If you want them to be independent across sprints, it's probably best to split them out as separate work types and link them via issue links/relationships instead.  

[Praveen_ Deepak _Synchrony_ consultant_]

thanks Chris Rogers

[Chris Rogers]

You bet, glad to help!

If you found my answer helpful, please consider marking this question as answered to help others find it when searching for similar solutions :)