I want to sum up story points of tasks and keep story and its tasks in sync

[坂加奈子]

hello

I want to sum up story points of tasks and keep story and its tasks in sync.

I tried the method below, but it didn't work.

https://community.atlassian.com/t5/Jira-Software-questions/Summing-up-story-points-from-Linked-tasks-to-story/qaq-p/2448964
https://community.atlassian.com/t5/Jira-Software-questions/Summing-up-the-story-points-from-task-that-are-link-to-a-story/qaq-p/2448864

I have tried using the method below as shown in the image, but it does not work.
Is there something wrong?

https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points

[Bill Sheboy · Accepted solution]

Hi @坂加奈子 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Are you asking about linked issues (as in those other posts), or a Story with Subtasks, or something else?

Kind regards,
Bill

[坂加奈子]

@Bill Sheboy 

Thank you for your reply.

Story has several Tasks.

I want to sum  story points of Tasks and set story points of Story.

please see further information below.

1. When: value changes for

　Fields to monitor for changes: Story Points

　Change type: Any changes to the field value

2. Issue Type equals

　Field: Issue Type

　Condition: equals

　value: Task

3. For: Stories (or other issues in Epic)

　

　4. Then: Edit issue fields

　　Story Points: {{issue.tasks.Story Points.sum}}

　

[Bill Sheboy]

What you describe is not default behavior; please clarify how you are using Jira issue types. 

This may be a case where you are using terminology which does not match Jira.  The default issue hierarchy for Jira Cloud is:

• Epic
  • Story, Task, or Bug
    • Subtask

And so an Epic can optionally have child issues of Story, Task, or Bug.  And those can in turn have Subtasks.

You are describing a Task being the same as an Epic, and Stories having Tasks as children.  Neither of those is accurate.

Please review this information, and then we can try to help once you describe the problem you are trying to solve: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/

[坂加奈子]

@Bill Sheboy 

Thank you for your reply.

Story create linked issues. its issue type is Task.

Tasks are tied to Story.

I want to automate the process of summing up story points of  Tasks and setting them to story points of Story.

please advise me this solution.

[Bill Sheboy]

Thank you for clarifying that you are using issue linking rather than parent/child issue relationships.

Are you using a Company-managed or a Team-managed project?  You may find that information at the lower-left side of the page expanding area.  This is important because Company-managed projects use the "Story points" smart value and Team-managed projects use the "Story point estimate" smart value for rules.

There is nothing built-in to do the summing you note for issue linking.  Instead your rule will need to gather the issues to perform the sum.

For example:

• trigger: value changes for Story Points
• condition: issue type equals Task
• action: lookup issues with JQL...
  • Please write JQL which can find the other Tasks for this same, related story.  As you are using your own method to relate the issues, you will need to create this JQL.
• branch: with JQL to the Story.  Please write JQL to find the Story for the trigger issue, Task.  As you are using your own method to relate the issues, you will need to create this JQL.
  • action: edit issue, setting the Story Points to this smart value
    • {{lookupIssues.Story points.sum|0}}

If you run into problems with creating the JQL, please contact your Jira site admin for assistance.  That will be easier than the community trying to do this without seeing your Jira instance.

[坂加奈子]

@Bill Sheboy 

Thank you for sharing your solution.

I use a Company-managed project.

Thank you for providing an example. I want to try it. Could you provide details on the JQL part?

[Bill Sheboy]

You have defined your own method of connecting the issues, with linking or other fields.  And so I would not know what to suggest for JQL.

Please identify some example issues you believe are related, and then use this information to create some example JQL for find the related Tasks: https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/

Once you have created and tested that JQL, it should be easier to create the rule.