Need Automation Rule to auto calculate story points in a story based on original estimates in hours?

[Shishir Agrawal]

I am trying to auto calculate Story Points for an issue type as story as and when the original estimate for the same issue type is updated. 

I have an active automation rule which sums up the original estimates of subtasks as child issues under stories to original estimate of a story. 

[Walter Buggenhout]

Hi @Shishir Agrawal and welcome to the Community!

A couple of things to help you further:

• for questions about automation rules, please share full details of the automation rule you already have in place (add screenshots of your full automation rule and - if you are getting errors - also from the rule's audit log, so we have a good idea where to start from).
• Explain in full detail what you expect the rule to do and where exactly you are getting stuck.

And also a couple of questions about your specific use case:

• Why would you try to derive story points from a time based original estimate? Story points are commonly used in teams to replace time based estimates. If certain teams combine both, they usually would do so the other way around - i.e. calculate a time based estimate based on the number of story points.
• Updating the original estimate of stories based on sub-tasks estimates is not really a recommended practice in Jira. I usually recommend reading up on this support article about work estimations in Jira for a bit more context.
• Considering time based estimates have no restrictions on what is entered (an estimate can be anything from 1 minute to several weeks), what is the logic you intend to use to convert estimates to story points?

[Brown_ Selena]

I can see a use case for this.  

In Product Discovery, progress bars are based on story points, not allowed by hours. Therefore, Every task I have that contributes to said progress, I have to manually add "story points" to the tasks so that the progress is as accurate as possible. For my teams, I use 1 point = 8 hours = 1 day. That's the only way that I can get close to showing accurate progress. 

If anyone has an automation that will show original estimate (in hours) divided by 8 (for my example), that may also solve the original author's question.

Thank you. :)