Posting of used hours (Story Points)

[Benjamin Kapelle]

Dear,

I'm struggleing with the new projects and story points. Within our day to day development we're useing weekly sprints. I'm planning sprints with estimated storypoints by our developers. So far so good.

Weekly we've to shift some allready started tasks (ex. 6 h used of 8 h estimated) to the next week. With the Jira standard I'm not able to evaluate the next sprint correctly because I'm not able to post allready used hours.

I've allready searched a lot at the community forum but have not been able to find any satisfactorily solution.

May someone give me a hint?

Thx in advance!

Kind regards

[Warren]

Hi @Benjamin Kapelle 

So you get to the end of a 1 week sprint and there are some tickets that are being worked on but not completed. I think you're asking about hours, but you mention story points as well, so I'll try to address both.

Hours

The Remaining Estimate field is now your friend, because in the example you gave above where you've used 6h of an 8h estimate, the Remaining Estimate field should be showing as 2h. But ... what you should also do at sprint planning is to look at each of these tickets that are carrying over, and ask the question whether that value is correct. The remaining value should then be adjusted. By then looking at the total of all the Remaining Estimates, you will be able to better plan the next sprint.

Story Points

Story points are an all or nothing thing - if the ticket isn't complete at the end of the sprint, no story points are "claimed" and they all carry over to the next sprint (even if it is 90% complete). It may skew your planning a bit if you look at velocity and how many story points to take into the sprint, but you can always bring in another ticket towards the end if you have completed everything.

I hope this helps make it all a bit clearer

[Benjamin Kapelle]

Hi @Warren ,

thx a lot.

"Hours" sounds like a viable approach. But I'm not able to find any field for Remaining Estimate. Where is it deposited? Will the usage of "hours" also have a corresponding effect on reports such as "BurnUp"?

Kind regards

Benjamin

[Warren]

Hi @Benjamin Kapelle 

Just to confirm, are you using the classic project or the Next-Gen project? If on Next-Gen, if you open the project sidebar, you would see something like the below

For the classic project, you need to use the "old" UI view (click on See the old view at the top of any open ticket), this doesn't seem to be available in Next-Gen projects at the moment

[Benjamin Kapelle]

Hey @Warren

we're talking about new projects. ;)

This would suite perfect. Is there any way to get this feature for new projects?

Kind Regars

Ben

[Aleksandra Klasa]

Hi Benjamin,

We might be able to assist you with this. Our app Worklogs - Time Reports for Jira offers the possibility to log time in any selected issue for any selected date and also set an original estimate to the issue within the same modal.

Please see the screenshot attached

When it comes to monitoring time logged by selected users in the appropriate period of time you can achieve this by using the suitable groupings and categorization in our app - Worklogs - Time Reports for Jira.

I hope this is helpful :)

[Benjamin Kapelle]

Hi @Aleksandra Klasa ,

thx. for your reply. I've got how to post used hours. But I'm still unsure where's the link betweend planned and posted hours.

For a better comprehension:

We're working with weekly sprints. Every developer is considered "fully utilized" after 24 hours of planning. I do this planning for several weeks into the future. But some tasks can't be completed in the same week. Therefore I've to shift tasks which are already in progress into another sprint. For example 8 h for task 123 have been estimated and planned for sprint X. While sprint X is in progress 6 h are used. 2 h are still ready to use, but can't be done in sprint X and have to be shifted into sprint Y. Now it would be really necessary to recognize that there are due to the sprint overhead 2 h left from task 123, but in my opinion I'm still unable to get an real overview. For the planning I now have to substract 2 h from the next 24 h weekly planning. So 22 h would be able for planning. Is there any way to deal with it?

Warm regards

Ben