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; } } }

Is it possible reset previous status check for transition condition?

Taylor Chappell_43og1t

I have a workflow in Jira Data Center that has a transition to a status with a condition that checks if the issue has been in 3 previous statuses (in no particular order). It also has a transition to the landing status in case edits need to be made, then the workflow has to start over.

My concern is if it goes through statuses 1 & 2, then goes back to start, but the team moves it to 3 (remember, no particular order required, but all need to happen sequentially) the final status will become available, but it needs to go through 2 & 1 again first.

If it helps clear this up, it's a pseudo approval for a software type project that is catered to multiple teams where the approvers may change or rotate. I am aware of other types of pseudo approval involving custom fields and I'm not seeking that solution at this time.

Accepted answers

Taylor Chappell_43og1t

It didn't seem possible to reset the condition for "Must have previously been in status". What I decided to do was use checkboxes modified in Post Functions to track approvals.

issue.set{
     setCustomFieldValue("Field 1", "Approved")
}

Using that script in the post function as well as a Post Function for "Clear selected fields" in my initial status, I was able to track approval progress as well as reset it. If people ask, I can post a much more detailed description.

All comments

Mohamed BENZIANE

Hi,

You could disable the possibility to go from status 1 to 3 without going through status 2. This way, all tickets will go through status 1, 2, and 3. If you can’t, you will need a script to check if the previous status respects the sequence.

Taylor Chappell_43og1t

The team requesting this is doing so to create fluidity between just the 3 approved statuses. So from "Pending Approval", it needs to go through 3 middle statuses in any order, and only then will "Approved" be available.

So I would need it to be able to go from A>B, A>C, B>A, B>C, C>A, and C>B at any point in any order. The kicker is that if it needs to go back to "Pending Approval", I need it to start the requirement all over again. They can't pick up where they left off.

Any ideas about where to start that script?

Taylor Chappell_43og1t

It didn't seem possible to reset the condition for "Must have previously been in status". What I decided to do was use checkboxes modified in Post Functions to track approvals.

issue.set{
     setCustomFieldValue("Field 1", "Approved")
}

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

workflow

data-center