Error while using lookupIssues JIra Smart Value to sum story points of items within an EPIC.
Here I've my approach on using lookupIssues to do the sum of story points in an Epic. But looks like LookupIssues ins't able to get the values of story points.
Am I missing something here? Can someone suggest how to improve on this?
Hello @Sanjog Sigdel
To use the {{lookupIssues}} smart value you must first use the Lookup Issues action.
This actually worked Thanks a lot @Trudy Claspill .
For future reference: I added the Look Issues like Mentioned above and then updated the Edit issue fields, Total Story Points like below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For future reference: I added the Look Issues like Mentioned above and then updated the Edit issue fields, Total Story Points like below:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Community,
has somebody managed to make this Automation in JIRA Cloud with the Parent changes from Epic link? I am struggling and getting only 0 and I am just int he begining of creating the full automation rule to cover the scenarios:
1. When new child is added
2. when parent is changed
3. when item is cancelled
4. Wen estimation changes...
Thanks in advance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @bilyana_karayaneva
To get the widest visibility to your question in the Community please create a new Question post.
When you add to an existing post the only people who see your addition are the original post author, the people who previously responded, and people that are Watching the post. On a post that is over a year old that is not very much visibility.
If you find an old post, like this one, that is relevant to your question, add a link for it in your new post.
Also, when asking for help concerning an Automation Rule please include the output from the rule execution Audit Log.
An additional debugging tip is to use the Log action to print out the number of issues found by the Lookup Issues action using the smart value {{lookupIssues size}}
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.