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

Legacy Automation migration fields on Automation

Àlex Costa_eqc187

Hello,

I am currently migrating a Legacy Automation rule from Jira Data Center to Jira Automation, but I am encountering difficulties due to differences in available fields and triggers.

In Legacy Automation, I used the trigger:

"Issue resolution changed", with a condition for "Resolution set" and "Resolution "Cleared"

However, in Jira Automation, I do not find an exact match for this condition. I understand that I can use the "Field value changed" trigger for Resolution, but I am unsure how to replicate the exact behavior, especially since some fields used in the Legacy Automation rule do not exist in Jira Automation.

Could you please guide me on how to best migrate this rule while ensuring the same functionality? Any recommendations or best practices would be highly appreciated.

Thank you for your support.

Best regards,

Accepted answers

Bill Sheboy

Hi @Àlex Costa -- Welcome to the Atlassian Community!

Have you tried using the if / else block with additional conditions:

https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html#Jiraautomationconditions-ifelseblockIf/Elseblock

And then use the Edit Issue action for each case to perform the updates.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Àlex Costa -- Welcome to the Atlassian Community!

Have you tried using the if / else block with additional conditions:

https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html#Jiraautomationconditions-ifelseblockIf/Elseblock

And then use the Edit Issue action for each case to perform the updates.

Kind regards,
Bill

Àlex Costa_eqc187

Hi Bill,

Thank you for your response.

The main issue I’m facing is that in Legacy Automation, it was very easy to handle this with the "Resolution set" and "Resolution cleared" conditions, but I can’t find a direct way to replicate this in Jira Automation.

In Legacy Automation, these conditions made it straightforward to manage resolution changes clearly and unambiguously. However, Jira Automation doesn’t seem to have a native alternative that provides the same behavior.

Is there a specific combination of conditions or rules I can use to ensure I cover both cases correctly?

I’d really appreciate any guidance on this.

Best regards,

Bill Sheboy

Did you try using the if / else and add conditions to test the values of the Resolution? That should lead to the same result as your original rule.

Àlex Costa_eqc187

Hi Bill,

Yes, I’ve already tried that approach, but I still don’t fully understand how to replicate the exact behavior of the "Resolution set" and "Resolution cleared" conditions from Legacy Automation.

In Legacy Automation, these conditions worked seamlessly, but in Jira Automation, I’m struggling to ensure that both cases are handled correctly without unexpected side effects.

Could you provide a more detailed example or clarify how to structure the rule to achieve the same logic? I want to make sure that both setting and clearing the resolution are handled properly, but I’m not entirely sure how to configure the conditions within the if/else block to reflect that accurately.

Thanks again for your help!

Best regards,

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

automation

data-center

legacy-automation