nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Retain the timestamp if it already exists.

Geethanjali S J

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.

Accepted answers

All comments

Trudy P Claspill

Hello @Geethanjali S J

Exactly how did you configure the custom field timestamp and how are you setting its value?

Geethanjali S J

Hi @Trudy P 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.

Trudy P Claspill

Do you have any third party apps/plugins added to your system that extend the capabilities of workflow customization?

Geethanjali S J

@Trudy P Claspill We installed JSU plugin nothing more than this.

For reference I am attaching snapshot.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server