You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
I have tried using the method below as shown in the image, but it does not work.
Is there something wrong?
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?
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
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:
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/
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.
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.
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.