Can "Estimated" field of sprint be "Time Tracking"? If yes then how to configure that?

[Sankalp Dubey]

I want to Estimate the scope of sprint on the basis of field "Time Tracking" and make Burndown charts on it. For that I need to configure the Sprint board field "Estimation statistic".

[Nic Brough -Adaptavist- · Accepted solution]

Yes, you can do this, but not exactly in the way you're assuming.

Time-tracking is not a simple field, it's an accumulation of several informational items on issues, and is actually made up of several things, some of which work very much like fields.  The main ones you'll want to consider to be a part of time-tracking are "original estimate", "time spent" and "remaining estimate"

For the sprint estimate, you need a numeric field, and the "original estimate" is the only suitable one within the time-tracking "field" (you burn down on the estimate, not what you've logged against it, or what you have left)

[Sankalp Dubey]

Thanks for your answer, it has helped me but now I'm facing another issue now.
After configuring Time Tracking for Estimation when I create a sprint and start it then I'm receiving a warning message like "JRA-000 do not have a value for the 'Estimate' field. Values entered after the start of the sprint will be treated as scope change."

[Nic Brough -Adaptavist-]

That's not an issue, it is just warning you that you are trying to bring an un-estimated issue into the sprint, and that if you then fill in an estimate later, it will look like scope change.

[Walter Buggenhout · Accepted solution]

Hi @Sankalp Dubey,

Time Tracking is not a field; it is a set of field containing original estimate, remaining estimate and time spent.

You probably want to estimate sprint scope off original estimate instead, while progress is then being measured from time spent and remaining estimate combined. Recommended settings would be like this:

Hope this helps!