Consider an Epic parent, have 3 child issue of Bug,Improvement and New feature and we want the rule to sum up all the story point of these 3 child issues to Parent's story point.
Hi,
The problem of tasks and subtasks being limited to a single level (you cannot create several nested subtasks). As a result, it is possible, for a tree structure of this type, to use the principle of Parentlink/Childlink
I've seen all of these answers (about "sum" pbl), which work great for task and subtask cases. On the other hand, it is impossible to run a procedure correctly with the ParentLink / childlink. For these cases, we fall into the same process. Do you have a solution for this type of case?
Example
child sheet = 10 and 20.
the first step is ok and the parentlink file is at 30.
if child 1 is modified (10->15), the parent changes to 45 (instead of 35).
Any idea ?
Thanks all.
Hi @Mohini Chandwani ,
There's this documentation that might help you implementing this without the need to use Lookup action (which is only available for Cloud instances):
https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points
Can you please take a look and see if it matches what you need?
Cheers,
Victor | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Victor.
In your link, this is with "{{issue.subtasks.Story Points.sum}}" ... and so, with only "subtasks". For me, "subtasks" is to list all issues in case of "Task / subtask". So, in this case we use "Parent" in branch to get task and "subtasks" to get all issues
In my case, we don't use task/subtask. Issues are linked with "parent link". Have you keywords for issues in context "Parent/Child" ? to get parent, we use "issue IN parentIssuesOf( {{issue.key}} )" ... but how to get all (and sum) about child's issues ? something like "childs" ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mohini Chandwani The following answer may help you with this: https://community.atlassian.com/t5/Automation-questions/Re-How-to-automate-the-sum-of-story-points-for-all-issue/qaq-p/1608031/comment-id/1067#M1067
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The link you shared in that I am unable to add "lookup" issue component, its not available for me.
There are two approaches I have figured out :
1.Find out all the child issues of Epic parent and sum up the "Story Points" of child issue and add up to Parent.
Problem : unable to find out the child issues using automation rule, how to get all those?
2.I tried using the {{triggerIssue.Story Points}} + {{issue.Story Points}} option but that continues to add like :
Story issue A = 12
Bug issue B = 10
Parent issue = 22 (first time it is correct)
This is fine so far but
Story issue A : 12 -> 15 (updated)
Parent Issue = 37 (not 25 like it should)
How to remove the Old Story Point and add new Story Point using smart values with rule.
Have read the articles, suggested to use join("+") that also does not work.
What can be the correct approach, please suggest.
Thank you for the immediate and valuable response.
Looking forward for more response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mohini Chandwani I have just replied on the other thread with a solution that will work in the Server version of Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Mohini Chandwani ,
There's this documentation that might help you implementing this without the need to use Lookup action (which is only available for Cloud instances):
https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points
Can you please take a look and see if it matches what you need?
Cheers,
Victor | Atlassian Support
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Victor ; not the good one because you use "task/subtask" and I use parent/child.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I post one here and I think it's not available now on DC
I have to wait for it ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.