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.

[Dave Theodore [Coyote Creek Consulting]]

There isn't one. You need to write one.  Fortunately, it's really easy. Read over the doc on backing up Atlassian tools and it should give you a good idea how it works. I would suggest disabling the automatic XML backup if it's enabled and using native database backups. Make sure you get the database data and the Data Directory or you won't have all of the data.