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

How can I create a rule to automatically switch tickets from one status to another?

Louise Rochais

Hello!

I can't create an automation rule to switch my tickets from one column to another and change their status.

Today I'd like tickets with MERGED status to automatically switch to TO BE TESTED as soon as a corrected version (version number to be tested by QA) is assigned to them. My tickets must change both column and status. Tickets must change from the CODE REVIEW column with status MERGED to the QA column with status TO BE TESTED.

I've checked my workflow, tickets can be switched from one status to the other without restriction

Here are the details of my rule :

Capture d’écran 2024-09-26 à 14.19.24.png

When: value change for --> Corrected version

State equal to --> MERGED

Then transfer ticket to state --> TO BE TESTED

I also tried without State equal to --> MERGED but it doesn't work either

Do you have any idea of my error?

Thanks a lot!

Accepted answers

Rudy Holtkamp

Hi @Louise Rochais ,

It seems like your rule is not triggered. Could you zoom in into the trigger?

Did you select something in the Change type field or in the For field?

If so, you might want to remove it and try again.

All comments

John Funk

Hi Louise - Welcome to the Atlassian Community!

Just some clarification - statuses are mapped to columns on a board. You can't say "I want to change the issue to status XYZ and move it to the Testing column". When the status changes it goes to the column mapped to that status automatically.

So, to your question - what error do you get? Can you share the audit log for when the rule fires?

shib saha

Hi @Louise Rochais , Welcome to the Community! With automation you can change the status of a ticket in the Jira project and ticket will automatically appear in the board column to which the status is mapped.

For automation, use the rule trigger as 'Field Value changed' and select the field name as 'Fix Versions' and add a condition to status equals to MERGED. In action use 'Transition Issue' and select the status as 'TO BE TESTED' and the automation will do the work.

Column on board is just for displaying the tickets from project with a specific status, make sure the status is mapped to individual column on the board, if same column has both the statuses in that case you won't see the ticket moving in column even after the status change.

Give it a try and let us know how it goes. Thanks

Auto Rule -01.PNG

Louise Rochais

Hi John, thanks for your answer.

I specified that I wanted to change column and status to best describe my situation, but I know that status takes precedence over column and my columns are well mapped. So when the status changes, the ticket should also change column.

I don't have a log history to share because my rule doesn't seem to be running. However, it is activated. I don't understand Capture d’écran 2024-09-26 à 14.59.25.png

Louise Rochais

Hi Shib,

Thanks for you answer

The rule you suggest is exactly the one I've implemented and it doesn't work. My rule doesn't seem to be running even though it's marked active on Jira. Capture d’écran 2024-09-26 à 15.11.29.png

Rudy Holtkamp

Hi @Louise Rochais ,

It seems like your rule is not triggered. Could you zoom in into the trigger?

Did you select something in the Change type field or in the For field?

If so, you might want to remove it and try again.

Louise Rochais

Hi Rudy,

Thanks a lot for your answer, I was able to solve my problem!
I was filling in the For = forward ticket field

John Funk

Is there another rule that is firing that is updating the Version? If so, update this rule so that it allows other rules to trigger it. You can find that on the Rule details page.
Automation Rule trigger box.png