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

Question about jira automation script

ADM Amar Msaid

i write a script that is triggered when the issue is created. i want to transitionne the issue to status that is not the first status in the workflow (see inserted image). The first status in the workflow (after the beginning) is ATT_VERIF_CGRH but i want to transitionne the ticket to the ATT_VERIF_PARH status when a certain condition is verified.

i get this message in the log and the ticket id tarnsitionned to ATT_VERIF_CGRH

error message.PNG

this is my workflow:

is it possible to have a second transition from the begining (1) to ATT_VERIF_PARH status (3) and resolve this error ?

Thank you.

Accepted answers

Trudy P Claspill

Hello @ADM Amar Msaid

Can you please show us the entire automation rule? Often problems are caused by the context in which the step executes. We can't know the context without seeing the rule.

Regarding your diagram, location 1 is not actually a status. It is just a visual indicator of the starting point in the status workflow.

Location 1 can have a transition to one and only one status. When the issue is initially created it will be set to the indicated status (2).

You can use your automation to then transition it to the next status (3), but you can't bypass status (2) based on how your workflow is constructed.

All comments

Trudy P Claspill

Hello @ADM Amar Msaid

Can you please show us the entire automation rule? Often problems are caused by the context in which the step executes. We can't know the context without seeing the rule.

Regarding your diagram, location 1 is not actually a status. It is just a visual indicator of the starting point in the status workflow.

Location 1 can have a transition to one and only one status. When the issue is initially created it will be set to the indicated status (2).

You can use your automation to then transition it to the next status (3), but you can't bypass status (2) based on how your workflow is constructed.

ADM Amar Msaid

Hi Trudy,

yes, my need is to use automation script to transit directly to status (3) when a condition is meet regarding data collected in the ticket. but it seems that we can't do this in a script triggered when the ticket is created.

i have the same error message when i use action to transit to status (2) even if the transition occure because status (2) is the next status after the begining of the workflow.

it is very easy to reproduce the case. just create a workflow with two statuses and write a script that runs when the ticket is created and that makes a transition to one or the other of the two statuses. you will get an error message and the ticket is still transitioned to the first status.

here the complete rule and error message

Trudy P Claspill

When an issue is initially created it is set to the first status in the workflow. The rule is executing after the issue creation is completed and the issues is already set to that first status.

You are getting the error that the issue can't transition to ATT_VERIF_CGRH because the issue is already in that status, and there is no transition to go from that status to that status.

You don't need to try to transition the issue to the first status as part of the rule. That is taken care of during the issue creation process. In your rule you only need to transition it to the next status - ATT_VERIF_PARH

ADM Amar Msaid

Hi,

My conclusion is that it seems to be impossible to transition a ticket to a status other than the first status of the workflow in a rule that is triggered when a ticket is created.

In my case, I cannot transition to ATT_VERIF_PARH status. That's why there is the second error message.

In a script that runs when a ticket is created, there is no need to use a transition action because the status after creation will be always determined by the workflow (the status linked with the beginning point of the workflow).

do you agree with me?

thank you.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-work-management

jira-work-management-cloud