Is there a way to achieve the desired effect with Automation Lite?

[Tigran Łaczinian]

We had used the Automation for Jira Lite (or rather it older version) in our tiny environment for years for a simple AutoClose feature for the issues which were on hold or resolved and were not updated longer than a week (with notification based on the comment being added to the issue). However the client asked us if we could add an additional notification a day before the issue will be closed and it caused us some problems so far, as the notification updates the issue so we could not use the old updated <= -7d filter. So we tried to add the property to the issue that the reminder was issued and the to close any issue which was not updated in the last day and had that property set. 

Unfortunately we could not use the property in the JQL as it is not indexed, we also found that we could not use the JQL condition as it must have a field on the left, not a value comparing to a value. The only way it looks to work now is using the Compare two values condition, but it is a PRO feature. At the moment we are trialing to check if it surely work as intended, but we are wondering if is there a way to achieve the same effect with Automation Lite.

[Iago Docando · Accepted solution]

From the top of my mind I would suggest using a custom field as a flag. This custom field wouldn't even need to be visible at any point.

If the reminder is sent (you can already do that with no problem whatsoever, you say) you should update this "flag" custom field. Let's say you update its value to "1"  (or "YES", or "SENT", or whatever).

Then configure another automation based on the update date of this custom field, if the value is "1" and it has been updated more than 24h ago (or the amount of time you want) then close the issue.

Note that you should also create another automation rule to reset the custom field value to its initial value when any other update is made (so the rule doesn't close an issue in the case that after the reminder people has worked in the issue again).

I hope it helps.