Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×We have universal transition statuses, I already configured a custom field timestamp at In progress status. Is there any way to not update the timestamp when moving to In progress if a timestamp already exists. When we come out of on hold status to In progress status, the timestamp is currently refreshed which skew our cycle time.
Hello @Geethanjali S J
Exactly how did you configure the custom field timestamp and how are you setting its value?
Hi @Trudy Claspill Thanks for the response.
Our workflow consists of four universal statuses: open, on hold, in progress, and Done. In progress timestamp must be recorded as soon as they enter the in progress status. By adding a post function at In progress transition, namely Update Any issue field in the field value as %%CURRENT_DATETIME%%, I was able to produce an in progress timestamp at the in progress status.
In progress Time stamp are captured when we move an issue from open to in progress status, and they continue to change when we move the issue back to open and again to in progress status. If a timestamp already exists, we must not update it when switching to the in progress status.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you have any third party apps/plugins added to your system that extend the capabilities of workflow customization?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill We installed JSU plugin nothing more than this.
For reference I am attaching snapshot.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Based on the following documentation for JSU, it seems that you should be able to define a Pre-condition for that Post Function to check if the custom field is empty.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even if we set a precondition it didn't work. The timestamp is updating even though the custom field is not empty.
Is there another to achieve this or any automation rules?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show us the configuration of the Post Function including the pre-condition.
Also please show us the workflow diagram.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.