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

Automation for when an issue's issue type changed from a certain issue types, change it back

İclal Aslan

Hi everyone,

I try to write an automation for when an issue's issue type changed from a certain issue types, change it back to what was it before. Let's say the issue type was x they changed it to y, change it back to x.

I can use JMWE(jira Misc Workflow Extension) or jira automation itself.

Any ideas how?

Thanks.

Accepted answers

Christos Markoulatos -Relational-

Hey @İclal Aslan

try something like this:

Screenshot 2025-10-14 102527.png

hope it helps!

Duc Thang TRAN

Hello @İclal Aslan

You can try with an automation rule where the trigger is:
When: Field value changes (Issue Type)

Then, add your condition(s) as needed.

For the action, choose Edit issue → Issue Type,
and use this smart value: {{fieldChange.from}}

More infos :

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Hope this can help

All comments

Christos Markoulatos -Relational-

Hey @İclal Aslan

try something like this:

Screenshot 2025-10-14 102527.png

hope it helps!

İclal Aslan

Hi,

Thank you. But when I edit the issue typw how can i make sure it changes to the old issue type?

Duc Thang TRAN

Hello @İclal Aslan

You can try with an automation rule where the trigger is:
When: Field value changes (Issue Type)

Then, add your condition(s) as needed.

For the action, choose Edit issue → Issue Type,
and use this smart value: {{fieldChange.from}}

More infos :

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Hope this can help

İclal Aslan

this worked perfectly thank you!

İclal Aslan

I was able to edit additional fields with @Duc Thang TRAN 's help. Thank you for your help! this helped a lot!

Bill Sheboy

Hi @İclal Aslan

Even though you have an automation rule to set the work item / issue type back, I caution against using it, and instead investigate why the types are changing by discussing this with your team, then try to solve that root cause instead.

The caution / reason is work item types each have their own configuration and workflow, and changing types can be complicated. This is why Atlassian has a specific UX feature to manage this, Move, which asks the person questions to help guide the change. An automation rule cannot stop and ask such questions. Thus, the rule must anticipate all possible problems and solve them as part of updating the work item. Without this, the best case is the rule just fails to make the edit and the worst is the work item is left in an unstable state.

Kind regards,
Bill

Duc Thang TRAN

Hello @Bill Sheboy

Thank you for sharing this item. I agree with your point — I remember a case involving this action.

The ticket got stuck in a status after the issue type was modified via automation and couldn’t move forward.

This reminds me not to suggest this action in the future

Bill Sheboy

One safer alternative with an automation rule is the REST API Bulk Move endpoint which may be called with Send Web Request action. I expect that to fail better when the move is not possible for predictable causes.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-move-post

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

automation