Problem: Item added to sprint A after sprint start is considered ‘added’ by Jira because it was added to an active sprint. Item carries to sprint B, Jira still considers it ‘added’. We want to consider this now committed for sprint B.
Considering it added in multiple sprints feels like it’s penalizing them in the ‘added’ category. Granted, carryover itself is not a good practice. But we’d like added to reflect as what was added after sprint start.
I need help with calculated measures for added defined as ‘added after sprint start.’
Hi, @wenlaw71
Welcom to the eazyBI community.
If the sprint A issue is added to the sprint after the sprint has started - it will be counted into measure “Sprint issues added”.
If sprint A ends and the issue is added to the next sprint B before the sprint starts, the issue will be counted in the measure “Sprint issues committed”.
The issue that shows as “Sprint issues added” is the issue that has been added to Sprint B after Sprint B started.
Please read more about Sprint issue measures here: Jira Software custom fields
If this is not the case, please write us into support@eazybi.com and please add the specific issue that is not counted correctly.
Kindly,
Ilze