Automation for Jira: Priority set within the rule is not copied when issue is cloned to another project

Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

When an Automation rule is created to edit the priority of an issue and the issue is cloned to another project, the set priority within the rule is not copied to the new issue.

(Auto-migrated image: description temporarily unavailable)
(Auto-migrated image: description temporarily unavailable)

Environment

Jira Cloud

Cause

Automation keeps a buffer to make things run faster, however, sometimes the buffer will not refresh quickly. Buffer can be a great thing to avoid any delay, but it can also cause a setback.

Solution

Add Re-Fetch issue data before cloning the issue

(Auto-migrated image: description temporarily unavailable)
Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.