Compare custom field from Initiative to Epic, and change value if Epic value is not matching

[Becci Watson]

Product: Jira
Version: Cloud
Project type: Company-managed
License: Premium
no plugins, just out of the box

Does anyone have an suggestions on how to do this?
I want to:

• run a schedule every hour
• For an Initiative
• Where a custom field is not empty (in the Initiative)
• Check if there are child Epics and don't run the rule if there are no children epics
• compare a custom field in Initiative with the same field in Epic
• If the Epic custom field doesn't match the same custom field in Initiative,
• Then update the Epic with the Initiative's value

I have tried to replicate this: Solved: Copy field priority from initiative to epic (atlassian.com)
But it appears there is a defect in the branch option drop downs such that a branch doesn't appear to allow a JQL to make the same query.  JQL query only available as extra condition.

[Becci Watson]

That's my first problem, the vertical scroll bar on that drop down doesn't allow me to scroll down to see the options yours does.

When I try to scroll down using the vertical scroll bar, it closes the dropdown list.
Trudy, Are you using Jira cloud or server version? 

[Trudy Claspill]

Can you show us the details of the Rule you created and provide more details on the specific error you are encountering?

It sounds like you're saying you can select JQL as an option for selecting related issues. I don't appear to have that problem in my Free Jira Cloud subscription. Can you show us a screen image of what you see?

[Becci Watson]

That's my first problem, the vertical scroll bar on that drop down doesn't allow me to scroll down to see the options yours does.
Trudy, Are you using Jira cloud or server version?

[Trudy Claspill]

Jira Cloud, Free subscription.

I have trouble with that scroll bar too. When I try to click on it the pull-down closes. So, once I click in the field I just use the keyboard arrow keys to scroll through the list.

[Becci Watson]

Thanks Trudy, I have logged a defect with Atlassian for the dropdown box.

In the picture above, I get and Error in the Branch JQL Query that says:
The character '{' is a reserved JQL character. You must enclose it in a string or use the escape '\u007b' instead. (line 1, character 79)

I am wondering if that portfolioChildIssuesOf comes from a plugin that is not Jira out of the box?

[Trudy Claspill]

I've not worked with Advanced Roadmaps in either Jira Server/DC or Jira Cloud, so I don't have any first hand experience with that function. I've done some searches and so far have not been able to conclusively find where that function comes from. If I find anything I'll post back here.

[Becci Watson]

Can this be referred to the Atlassian product manager who would know?

[Bill Sheboy]

Hi @Becci Watson and @Trudy Claspill 

I noted a couple of things in your JQL to try:

The help shows using quotation marks around the key for the portfolioChildIssuesOf() function: https://support.atlassian.com/jira-software-cloud/docs/search-for-advanced-roadmaps-custom-fields-in-jql/#Child-issues

And, smart values are case and spacing-sensitive.  Please try changing to use this for the trigger issue value:

{{triggerIssue.key}}

Kind regards,
Bill