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 to skip JIRA status on a speicified condition?

Hisamitsu Koga_cv95ul

Is it possible to skip JIRA status on a specified conditions?

e.g. if "Resolved" is clicked in case "Componets" filed is "A Team", skip to move to status "Resolved" and change status "Closed" directly. if it is possible, please let me know how to do in details.

Accepted answers

Tibor Hegyi [META-INF]

Is the component field filled in the transition view or stored in the issue prior to clicking Resolved?

Case A: component is set before clicking Resolved:

Add an additional transition to the workflow, also called Resolved. This will move the issue to Closed.
Add a Condition to the transition that checks if Component is set to "A Team".
Add a Condition to the original Resolved transition as well if Component is not "A team".
This way the two Resolved transitions will be exclusive and only one will be shown.

Case B: component is set in the transition view

I recommend you use an addon for that.

MISC Workflow Extensions has a postfunction: Transition Issue that can be used to skip to another status conditionally if the component criteria is met.

ScriptRunner for JIRA is also a powerful add-on that has a Scripted Postfunction that can be configured with FastTrack Transition Issue built-in script. It will move the issue to another status conditionally.

MISC or ScriptRunner can be used to implement a solution for Case B but it will be a solution as well for Case A.

All comments

Tibor Hegyi [META-INF]

Is the component field filled in the transition view or stored in the issue prior to clicking Resolved?

Case A: component is set before clicking Resolved:

Case B: component is set in the transition view

I recommend you use an addon for that.

MISC Workflow Extensions has a postfunction: Transition Issue that can be used to skip to another status conditionally if the component criteria is met.

MISC or ScriptRunner can be used to implement a solution for Case B but it will be a solution as well for Case A.

Hisamitsu Koga_cv95ul

Hi Tibor,

Thank you for your prompt anwer. Appreciate too much.

Case A, first of all, two same transition names can be existed? I have tried to add an additional same transition, but it can't be accepted since it is already present.

Used ScriptRunner and my request can be performed by FastTrack Transition Issue built-in script.

Jeremy Gaudet

You can't have two transitions with the same name, but you can use workflow properties to make it so they both appear with the same name. The properties are "jira.i18n.submit" and "jira.i18n.title", and you give them values that map to keys that represent the translated values. The default workflow's transition for "Resolve Issue" has those properties, I believe they are set to "resolveissue.submit" and "resolveissue.title".

However, for this case, it seems like there is no reason to name the transition "Resolve", when it's going to perform a "Close", you could just name it "Close".

I think the split conditional transition is a slightly cleaner approach, as it doesn't add the resolution transition to the issue's history.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

jira-core