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

Automatic change in Transitions (Status) in JIRA Workflow

Gaurav Nawathey2

Does JIRA has the Functionality to automatically change the Status (Transition) of an Issue based on Post-Functions. I am aware, we can change the Resolution of Issues, but it does not allow to Change the Status of an issue.

Alternatively, is there any plugin which helps in changing the status of an issue; if not a post-function.

Accepted answers

All comments

C.Faysal {CFcon}

hi gaurav,

a transition moves the issue to a different "status"

i wonder what the backgroud of your question is about...

https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

i.e.

Step A (Status=Open): possible transitions are

"Start" links to "status = In Progress"
"Reject" links to "status = REJECTED"

of course postfuctions can update issue fields too

what exactly do you mean?

Nic Brough -Adaptavist-

I suspect this question is actually one about automation. This crops up irregularly because it's not obvious that Status (of an issue) is NOT a field, it is an indicator of position in the workflow.

Developers keep adding post-functions to Jira that say "in this case, change the status", without understanding that the point of a transition is to move from state A to state B and that post-functions run inside a transition, so subverting the transition end-point from the inside is asking for trouble.

Gaurav is steps ahead of most here, stating "cannot change status in transition". Technically, you can, but I've yet to see stable working code that does it (and I've spent a lot of time cleaning up the horrid messes made when people try it). So I think the answer here is either

Do what C.Faysal says and set up multiple transitions

Use a listener to capture the event that the transition fires, and tell the listener to execute a second transition when it detects the right circumstances. Events are processed AFTER transition completion, so they're perfectly safe to trigger another transition.

unknown

I'd like to have a rule along the lines of "If status has been 'Awiting Client' for 30 days or more then close". Can this be automated?

unknown

I'd like to have a rule along the lines of "If status has been 'Awiting Client' for 30 days or more then close". Can this be automated?

Nic Brough -Adaptavist-

Yup. Set up the workflow as above, then write a filter that says "status = awaiting client and updated < -30d", then use a jelly escalation script to trigger the close transition.

See https://confluence.atlassian.com/display/JIRA/Jelly+Escalation

unknown

Thanks Nic - I've not yet tried Jelly scripts, but perhaps this is what will tip me over the edge.