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

Skip the same transition on the target workflow and automatically move tickets to "TO DO".

jira_admin_cu

Hi Team,

We have the same workflows and status names for different issue types within one project because we added conditions and post functions to each workflow based on their issue type.

When moving a ticket from one issue type to another within the same project, the workflow status remains the same because both the source and target issue types have the same status (this is a common feature). Do you have any suggestions on how to bypass the matching status for the target issue type and instead transition it to the first status of the workflow?

Accepted answers

Ram Kumar Aravindakshan _Adaptavist_

Hi @jira_admin_cu

If you are looking for a simple approach to Transitioning the issue back to To-Do, for example, based on the Issue Type change, I suggest looking into ScriptRunner's HAPI.

With HAPI, you can perform a Transition to any status based on the condition you set. To get started, refer to this HAPI documentation.

Let me know how it goes.

Thank you and Kind regards,
Ram

All comments

Nacho Moreno Ortega

Hello Lakshmi S,

I am Nacho and i am part of the Decadis team.

Is it a possibility for you to use a third party app?

If so, with our app Jira Workflow Toolbox, the post function Transition issue automatically executes a specific transition on the selected issues or transitions issues to a selected status.

If you need assistance on how to implement it, please feel free to create a ticket in our support portal and we will gladly assist you.

Best regards,

Nacho

David Nickell

1. If this is something you know you will be doing regularly, you should be able to create an automation rule based on the issue moved trigger.

2. If you prefer to be more "hands on" in the process, you could set up a new status on sending side and then transition to the status before your move. The benefit here is you could also have a transition screen available to capture any reasoning you might want to retain for the move.

3. Finally -- I've used the concept of a "hub" status before where you can work around a workflow using a status all other statuses can reach (e.g. "Bypass"). You can capture the reason for going to "Bypass" with a transition screen. And then have a special permission for moving out of "Bypass" to anywhere else in the workflow. This is especially handy for Sev 1 type fixes where clicking each step in the workflow is sometimes unnecessary. This "Bypass" could be the status you transition to before your move to a new issue type.

1. (automation) is the most streamlined and you can certainly audit the results. "2" and "3" are truly old school / pre automation tricks.

Good luck.

Ram Kumar Aravindakshan _Adaptavist_

Hi @jira_admin_cu

If you are looking for a simple approach to Transitioning the issue back to To-Do, for example, based on the Issue Type change, I suggest looking into ScriptRunner's HAPI.

With HAPI, you can perform a Transition to any status based on the condition you set. To get started, refer to this HAPI documentation.

Let me know how it goes.

Thank you and Kind regards,
Ram

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-data-center

workflow

status

data-center

jmwe