Calculate the weekly story points added
Asked by Rutuja Ghadge:

I have team who updates story point on weekly basis on issues in jira. if this week they have a task called AB and the story point updated is 5 and next week story point updated will be 8 and the next week actually story points spent will be 3, so total as of week 2 is 8 if I want the individual value when it is updated, how can I automate that is jira without created any new field every time they update the story point I should get a weekly report by Friday as to how many story points are added and what was the previous value


Answers:
author: Bill Sheboy
body: Hi [@Rutuja Ghadge](/t5/user/viewprofilepage/user-id/5573468) -- Welcome to the Atlassian Community!

First things first: I hypothesize you are observing changes to issues' story points *during a sprint* and thus have concerns. This could be a symptom of several root causes, such as: challenges with backlog refinement, scope change, skill gaps, team focus, team fear of communicating impediments, etc.

Before implementing any reporting, I recommend having a team discussion during a retrospective to acknowledge the symptom, use root cause analysis methods to uncover what is happening, and develop experiments to help improve.

Back to your question...

There are several ways to do this without adding a custom field, with varying degrees of cost, complexity, security, and easy of use.

1. Investigate marketplace addons which can do this type of reporting
2. This field-change information is already in the issue history. And so with the REST API the changes could be checked, either using an externally built application or an automation rule. Using a rule could be challenging if there are many issue updates, requiring paging through the history data.
3. Using an automation rule triggered on a change to the field, detect if the value was changed (versus added the first time), and add a comment to the issue. Then review the comments once a week manually.
4. Using an automation rule, again to detect changes, log the changes in an entity property. Then weekly run another rule to report the results and clear the entity property for a reset.

Again, I suggest discussing this symptom with the team before building / buying any reporting.

Kind regards,  
Bill

comments: author: Rutuja Ghadge
body: Thank you so mucn, can you please share a step by step guide as to how I can do the automation


author: Bill Sheboy
body: This community is a place for people to learn, share ideas, and to seek help with Atlassian tools. And, successfully using automation rules requires learning and experimentation.

I recommend you first learn a bit about creating rules, then try to create the rule to meet your needs. If you run into challenges, post images of your rule and the audit log details so the community can offer help. Your Jira Site Admin should also be able to help with automation rules.

I already provided some outlines to build the rules, and to get you started on creating your rule, please refer to these documentation and example sources:

* <https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation>
* <https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/>
* [https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all\&page=1\&pageSize=20\&sortKey=name\&sortOrder=ASC](https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC)
* <https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/>


Tags: cloud

jira-cloud