I am trying to copy three fields automatically from the initiative to the epic - I am not able to use any branching (see example in screenshots). Do I need to use smart values?
Instead of branching on children (which only considers sub-tasks) you should branch on JQL and use this as your JQL to consider all epics under the initiative:
issuekey in portfolioChildIssuesOf("{{triggerissue.key}}") and issuetype = epic
Cheers,
Rudy
Edit: fixed the JQL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is a ( too many in the JQL you've used.
You don't need to use () at all if you only use the AND clause.
Only for the function portfolioChildIssuesOf and for the IN clause. You can remove the rest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rudy Holtkamp Sorry if my screenshot was confusing, I am using the exact syntax from your earlier post:
portfolioChildIssuesOf("{{triggerissue.key}}") and issuetype = epic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't know why the error log is acting like I have more in the JQL than that
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.
Hi @Michelle Rose ,
My apologies, I did not copy paste the whole jql:
issuekey in portfolioChildIssuesOf("{{triggerissue.key}}") and issuetype = epic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rudy Holtkamp Thank you, that worked! How would I write the JQL if I wanted to copy fields from an epic to its children? I tried doing branching and that didn't work, so I am trying JQL instead.
This is what I have so far and I'm getting error messages:
issuekey in ChildIssuesOf("{{triggerissue.key}}") and issuetype in (task, story, bug)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Michelle Rose you made a mistake in the JQL use portfolioChildIssuesOf instead of ChildIssuesOf:
issuekey in portfolioChildIssuesOf("{{triggerissue.key}}") and issuetype in (task, story, bug)
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.