create a set of Jira automation rules for story points to automate calculation of different points.

SAzaruddin_mp April 2, 2024

We need help to create a set of Jira automation rules for story points to automate calculation of different points. We have a company-managed project.

Issue structure:
Level 1: Epic
Level 0: Task
Level -1: Subtask

Our Fields:
- Story points
- Story points remaining (Story points minus Story points from Closed tasks)
- Value points (value to business)
- Return of investment (ROI points) = Value points / Story points remaining

We need rules to calculate:
1. Total Story points / story points remaining of parents from the lowest level if story points of children are changed or status changes.

We already have a rule that semi works for this, but it does not update on all levels. For example, if we edit story points of a subtask, then the parent-task will be calculated correctly, but not for the Epic.

2. If user changes a parent tasks story points, but children-tasks contains story points, then an automation rule should recalculate the story points to override the users changes.

3. If possible, we also want to include "blocked by"-tasks in the calculation for sub-tasks.

Not sure if this is possible to achieve.

4. If value points are 0 or empty, or story points remaining becomes 0/empty, then ROI points should be set to empty

5. If value points and story points remaining is greater than 0, then it should calculate ROI value (Value points / Story points remaining)

2 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 2, 2024

Hi @SAzaruddin_mp 

All of the things you describe seem possible with automation rules.

This scenario seems quite specific to your needs, and I recommend you try the following:

  • First thing: do not work on this alone
    • Complicated solutions like this need to be understood by multiple team members
    • Partnering with others will lead to better ideas, faster implementation, and more reliable maintenance of rules
  • Clarify what problem are you solving by doing this? 
    • That is "why do this"?
    • Confirm how the team / org will behave differently if you had this information right now
    • Those things will help you know the order to work on these, and if they even solve the original problem
  • Write down examples of what you expect the results to be for each calculation.  This will help to create test issues when validating your rules.
  • Work on each item from your list, one at a time, confirming they work fully in a "rule testing" project, before proceeding to the next calculation.  When done, copy the rules to your "production" project.
  • Some of your items, such as #1, require the actions of one rule to trigger another.  This feature is disabled by default to prevent errors and looping.  You may enable that with the "Allow Rule Trigger" option in the rule details.  I recommend caution using that, given the number of calculations you describe.
  • Your item #3 item notes including linked issues with the type "blocked by".  Although that is possible, it will cause double counting of the values in different parents.

If after doing all of that, you observe problems in a rule, please post an image of the complete rule, the audit log details, and describe what is not working as expected.  That will provide context for the community to help.

Kind regards,

0 votes
SAzaruddin_mp April 2, 2024

Hi @Bill Sheboy 

Thanks for your response. 



Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events