Hello,
I have scanned all post about summing up Epic's tasks and still didn't find solution to my problem - while changing "Story points" value on child task, rule executes and show that did the modification but nothing is actually changing in Epic (parent) task.
Funny thing is, that for my other JIRA account (other Client), both solutions are working.
I used that one: for editing field: {{lookupIssues.Story Points.sum|0}}
I also took another recommended approach - still not working:
Any idea?
Hi @Lewandowski, Mikolaj -- Welcome to the Atlassian Community!
Is this for a company-managed project (CMP) or a team-managed project (TMP)?
CMP use the "Story points" field and TMP use the "Story point estimate" field, and so the correct field must be used in the lookup when summing for such a rule to work.
Kind regards,
Bill
Hello, company is using Story Points field:
when I've changed rules to use "Story point estimates" as suggested, rules seems not even recognizing any changes on the field values.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I was suggestion if you are using a team-managed project to change the values, however it appears you are not.
Smart values are case-sensitive, so check if this is the problem by updating the edit to this:
{{lookupIssues.Story points.sum|0}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, thank You.
When I am using
{{lookupIssues.Story Points.sum|0}}
or, as suggested
{{lookupIssues.Story points.sum|0}}
the same thing happens - "Success" but nothing is changing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please try writing that value to the audit log to see what appears...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on the error it looks like your epic may have stories from other projects and if that is the case you need to change the scope to multiple projects in the global automation settings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Fabian Lim
thank Your for Your reaction, but tasks were created in the same project and all having the same X5 prefix:
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.