Sprint committed issues

The function in Eazybi is not accurate for sprint committed issues:
( [Measures].[Transitions to],
[Transition Field].[Sprint status],
[Sprint Status].[Active],
– An issue was in a sprint at a sprint start time
[Issue Sprint Status Change].[Future => Active]
if an issues is a part of the backlog before the sprint started it counts it as committed
any idea for another way to measure sprint committed issues at a sprint start date?

Hi @Anna_Chernov,

The Sprint commitment is what a team has agreed to work on at the very beginning of the Sprint. The planning period may differ for different teams, but it is usually days or weeks before the Sprint.

Measures “Sprint Issues committed” and “Sprint Story Points committed” show issues that are already added to the Sprint when the Sprint is activated; it does not matter when the issue was added to the Sprint (five or fifty days before the Sprint is started) as long as it is before sprint activation date.
If you add a Time dimension to the report, you can see that both measures, “Sprint Issues committed” and “Sprint Story Points committed”, show value only on the date when Sprint is started.

If you want to see issues or Story Points that are added after the Sprint is activated, then you might want to use “Sprint Issues added” and “Sprint Story Points added” measures.

For more details, please see the measure description in the documentation: Jira Software custom fields.

Zane / support@eazyBI.com