Problem with time estimation

[Farida Musayeva]

Hello,

We use time tracking in the project (original / remaining estimate) and work in sprints.
I am planning an activity for Sprint A, setting the original and remaining estimate to 2 PT.
At the end of Sprint A, the process was processed but not completed.
The remaining estimate is recorded with 1 PT.
Now I want to plan sprint B and drag the issue of sprint A from the backlog to sprint B.
From my point of view, only the remaining estimate should now be counted in the time tracking for the sprint.
However, the original and not the remaining estimate is used here again.
Is that a mistake or I need  to set something different?

[Bert Dombrecht · Accepted solution]

Hello Farida,

From your question, I get the impression you are mixing story point tracking and time estimation.

If you are using story points, there is only one story point estimation field provided. Your velocity from sprint to sprint will be measured against these estimates. I believe Jira does not consider the scenario where an issue with story point estimation is only partly done in a sprint. 

'Original estimate' and 'Remaining estimate' are specified in minutes, hours, days, or weeks. The remaining estimate can be calculated if time is logged on an issue. This does carry over to a next sprint, so you can base your sprint contents on the Remaining Estimate field.

Some more references: 

https://support.atlassian.com/jira-software-cloud/docs/configure-estimation-and-tracking/

https://community.atlassian.com/t5/Agile-questions/Can-I-track-Story-Points-remaining-when-an-Issue-rolls-into-a/qaq-p/788599

I hope this helps.

[Bert Dombrecht]

One more detail: If you are using time estimates, you can see the remaining estimate sum of your sprint by clicking on the '...' (View Summary of Assigned Work) below the Sprint Name in the Backlog section of your Scrum board.

[Farida Musayeva]

Thank you for the reply and help :)