How to check (and reject) tickets which have not had a field updated since creation.

[GC]

Hey guys help from the community on this is much appreciated! 

Here is the scenario:

I have a project with some custom fields that need to be updated by the time the tickets they are in are closed. 

These fields are free-text, created with a default value within the configuration scheme which we use as a template for the kind of information we expect to see in the field.

I want a way to reject tickets that are transitioned into 'done' if these fields haven't been updated with actual information (ie the template is cleared and new info entered)

I can see that in the workflow transition validators, I can choose to set a validator to reject the transition if the field is left blank or if the field isn't updated on transition but neither of these apply to my situation as the field update could happen before the transition which I still want to allow. 

I tried to set up an automation but I'm not able to find a field condition that would check for a field update after creation, and I'm not sure how to express this in a JQL.

Does anyone have any clue as to how I could express this in a JQL or a different solution that doesn't require something like ScriptRunner or any other 3rd party app?

Thank you! 🙏🏼

[Daniel Eads]

Hey Gaj,

We have several Data Center customers doing this where they need end-to-end encryption for compliance reasons.

However, my personal recommendation is to use a local reverse proxy on each node if you can manage HTTP between your reverse proxy and Tomcat on the local node. nginx does a better job at terminating SSL than Tomcat, and the setup is a little more flexible than purely Tomcat only. For example, if you're using nginx Plus as your load balancer, nginx on each node would provide additional reporting and metrics to the load balancer about each node's health.

The tricky bit with doing it in Tomcat is that you'll need to ensure each node correctly imports the certificates you're using (and you'll need to do this each time you scale out to a new node). The Java keytool can be a bit fiddly to work with.

Cheers,
Daniel