Hellow Jira savvies,
Based on several community guides, I've created an automated rule to calculate the story points under an epic, and update the epic story points filed accordingly.
The rule seems to be working, but nothing changed in the Epic story points field:
My Automation rule:
1.
2.
3.
4.
I will appreciate your input on where the problem is at.
Thanks,
Ori
I believe the issue is with the use of "subtasks". Task, Story and Bug types are not "subtasks". Try the following...
{{lookupIssues.Story Points.sum}}
There are several posts discussing the method. Here is one I found where Bill did a good job of providing details. How-do-you-sum-up-story-points-to-the-epic-using-jira-automation . There are a couple others in the links under Related content to the right.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes follow that other thread and let me know if you get stuck. I can create a rule and test for you later today when I have a moment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That would be amazing!
I followed the post you shared and the result is the same.
could it be related to the fact that I'm using Jira Could?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No it should work for cloud just fine. Here is another thread offering a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ori Gal
Before your Branch please try adding a Lookup Issues action with JQL to match the sibling issues (with the same epic parent). Then your edit should work.
Please note:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Assuming your trigger issue is a Story that is in an epic, please try to match on the key, such as:
issueType IN (Story) AND "Epic Link" = {{triggerIssue.Epic Link}}
I encourage you to review the linked post that Jack provided as there are some edge-cases to watch for.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.