Story Points da issue na Sprint passada

[JOSE VALIM]

Boa tarde a todos, espero que estejam bem

Imagine o cénario:

- Fluxo de navegação de issues: Backlog -> Dev -> Teste -> HML -> Pronto

Na Sprint 1 possuo 3 cards do tipo historia sendo:

- Historia 1 - 8 Pontos

- HIstoria 2 - 3 Pontos

- Historia 3 - 13 Pontos

Todas as historias estão metrificadas assumindo que o valor do SP é referente ao fluxo todo relatado acima.

A Sprint 1 fechou e a História 2 não foi entregue. Ela ficou no status Teste e tombou para a Sprint 2.

Na Sprint 2 teremos:

- HIstoria 4 - 1 Ponto

- Historia 5 - 5 Pontos

- Historia 3 - 5 Pontos (Como foi concluido o desenvolvimento ficando pendente apenas testes e homologação, na próxima Sprint ela vem apenas com a pontuação restante).

Quando visualizo o Relatório da Sprint, as pontuações estão corretas da Sprint 1, mas quando vou para um filtro personalizado, a Historia 3 que na Sprint 1 teve 13 pontos, apresenta apenas 5.


Finalmente a pergunta é: Como capturar a pontuação da HIstoria na Sprint corretamente, tendo em vista que pelo campo SP ele apresenta sempre o último valor.

[Danut M _StonikByte_ · Accepted solution]

Hi @JOSE VALIM,

You can see the value that the Story Points field had for an issue during a specific sprint in Jira's Sprint Report, which uses historical data. 

However, you should not change the Story Points value to reflect the remaining work, as this will affect the team's overall velocity calculation and will no longer represent the actual complexity/size of the entire story.

During Sprint Planning, the team should take the remaining work (equivalent to 5 SPs in your example) into account when making the commitment, but the size of the story itself should remain unchanged at 13 Story Points.

Danut.

[Gor Greyan · Accepted solution]

Hi @JOSE VALIM

Welcome to the Atlassian Community!

What you're seeing is okay. The Story Points field stores the current value of the work item, so if Story 3 was originally 13 points and you later change it to 5, a standard JQL filter/export will show 5.

The Sprint Report is different because Jira uses historical sprint data to show what was committed and how the estimate changed during the sprint. However, Jira doesn't provide a native JQL field, such as “Story Points in Sprint 1,” that you can use in a standard filter.

If you need this information for custom reports, one option is to use the work item's changelog/history via the REST API to determine what the Story Points value was at a particular point in time.

Another practical option is to create a custom number field, for example Initial Story Points or Committed Story Points, and use Jira Automation to copy the Story Points value into it when the work item enters/starts its first sprint. You can then keep that field unchanged.