-
Sub-task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
None
-
False
-
ACM-633 - RHACM Assembly and Channels for Market Consumption
-
-
Jira can automatically calculate velocity per sprint, but there are nuances that need to be considered:
- QE’s workflow creates sub-tasks for stories, so a story becomes shared work between Engineering and QE.
- QE will generally be doing testing in the 2nd sprint of a Train.
- This means a Story that is dev-complete by the Sprint 1 in a Train will need to move to Sprint 2 of a Train, and then closed in that 2nd sprint when all QE Sub-tasks are complete.
- There’s nothing fundamentally wrong with the above except that velocity calculations are no longer automatic since a Story remains open at the end of Sprint 1.
- Idea: is there a way to have Jira calculate velocity based on a story being in REVIEW state vs Closed?