How to track individual Issue's "Time spend against Story Points

[Anantharaj]

How to track individual Issues' "Time spend against Story Points

[Jack Brickey · Accepted solution]

Hi @Anantharaj , welcome to the Community. Can you elaborate on what you want? Are you trying to assess the actual "time" (hhmmss) an issue took to complete?

[Anantharaj]

@Jack Brickey  -For instance,  I have a task (JIRA) with a story point 10.  this task is assigned to a Assignee in a SPRINT. I want him to update his time consumption in JIRA in such a way that i.e. how many story point of work has he completed what is the balance Story point he still left over.  
If I can track his balance of "Story Point" left (as per above), it may help me to think/decide whether I can allocate additional task/JIRA task for this same person.

How do I track the consumed story point cum left over story point in JIRA? 

[Wojciech Wardaszko]

Hi @Anantharaj

Welcome to the community.

I think it depends on how you assign value to your Story Points. As far as I can tell, they are used in a non-linear growth ratio, so a story that has 12 Story Points may take way longer to complete than 12 issues that only have 1 Story point.

Also, where in Jira would you like to track the remaining story points of a user? Users cannot store such values, so you'd need a separate Jira issue, probably named using the User.DisplayName - Sprint.Name pattern and there have a custom field to store available story points for that user. 

You would also need an automation rule that would trigger on the Work Logged action and first link that issue to the user-sprint issue with some conditional logic, then use the branch mechanic to actually update the value on that user-sprint issue by calculating the story points deduction based on the {{worklog.timeSpentSeconds}} value.

If you want to try that approach, you're definitely going to learn a lot about Jira Automation in the process, but by all means and purposes, this should be doable, unless I'm missing something.

Cheers!

[Jack Brickey]

Hi @Anantharaj , story points are intended to be a means of estimating the scope of an issue/task for planning a sprint (what-are-story-points ). They are not effective at tracking actual consumption. There are sprint reports that illustrate how many SP are complete/remaining but that is purely based on the estimation. At the end of the sprint, the team should evaluate each issue to understand if the estimation was accurate, and if not learn from that for future planning purposes. If desired, you could add a custom field, where the user could place a story point value of the actual amount of work the issue took to complete. If you wish to track actual amount of work consumed while working issues you should consider leveraging time estimation.