-
Suggestion
-
Resolution: Duplicate
-
None
Specifically, I want to have at least two types of SubTasks that when created automatically are linked to the parent story or bug. The default SubTask works fine, but the additional SubTask that I need is for Bugs. More specifically Bugs that are directly and automatically related to the specific User Story being tested. We will use the Sub-Bug for bugs raised during In Sprint testing that focuses on testing of User Story Acceptance criteria. We will then use the separate and independent Bug issue to log Regression defects. By default In Sprint bugs are related to a specific User Story in the current Sprint and are expected to be fixed during the current Sprint. That's a goal. However, Regression bugs are not related to a specific User Story by default and are added to the backlog and prioritized along with everything else in the backlog. Regression defects can still be related to one or more Stories if needed and they can still be addressed in the current Sprint if they are critical for the completion of the current Sprint.
- duplicates
-
- Under Consideration
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-91377] Need ability to define different types of SubTasks
I believe this issue is a duplicate of JSWCLOUD-20901 – Allow the creation of Multiple Sub-task issue types in Team Managed projects
I recommend that watchers of this issue vote on and watch the above issue. So that votes aren't split, I believe this ticket should be closed, but I will wait a week before taking any action in case anyone thinks both issues should continue to exist. Thank you!
As per this comment I am closing this ticket.
If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.