Field edit automation is bypassing issues in the lookup Issues list.

[Danno]

Per @Trudy Claspill I am starting a new request for help with this automation issue. The original question was from this conversation: How can I produce a specific kind of aging report without add-ins. 

My automation works well except it does not process all of the issues found in the lookup. There are less than 100 issues so I don't think that is the problem.

Here is what I have so far:

The search in the lookup Issues validates to a filter I am using to find every open "Discrepancy Report" which returns 84 issues. Below are issues that do not get updated.  The issues that have the blank space in the far right column do not get processed for some reason which has me baffled. It's not an editing permission for the project since it has processed some of them. Any suggestions?

I can post the rest of the automation rule although it seems to be working correctly. The audit log indicates that the rule sees every issue, but if you look at the log you will see that the issues above that haven't been updated in the right-hand column are not in the log results.

[John McKiernan · Accepted solution]

Hi Marco, 

thanks for your question (and the clarity with which you have asked it!) 

With Automation for Jira, this is not something we can do at the moment. We have an existing improvement issue to support multiple levels of hierarchy. I have added a vote to it on your behalf. 

https://codebarrel.atlassian.net/browse/AUT-309

Cheers,

John 

[Edwin Stol]

Hi @John McKiernan1,

We managed to resolve it as follows, with a combo of ScriptRunner and A4J:

[John McKiernan]

Hey Edwin,

this makes a lot of sense. Glad you found a workaround and thanks also for sharing it on the community :)

Cheers,

John 

[Mike Headley]

In case anyone's looking to do this on a company-managed Jira Cloud instance: I used the same general structure of the previous answer and added on / updated a few of the queries. Interestingly, smart values seem to have come a long way and I was able to do things well outside of the documentation. For example, I was able to grab the Theme name from the Epic level using the smart value {{triggerIssue.parent.parent.summary}}

For context, I wanted to map 3 custom fields whenever any of the issues in the hierarchy update their parent link:

Portfolio = Theme

Program = Initiative

Project = Epic