Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-383

Transition Issue Action Fails to copy Trigger Issue Status from Team-Managed to Company-Managed Project

    • Severity 2 - Major
    • 0

      Issue Summary

      In an automation rule, using the action Transition Issue to copy status from a team-managed project issue to a company-managed issue project fails with a "Destination status could not be resolved" error.

      Steps to Reproduce

      1. Create a rule to manually trigger from a team-managed project.
      2. Set the rule to copy to a destination issue is in a company-managed project (such as created by a clone action).
      3. Add the action Transition Issue with the destination status set to Copy from trigger issue

      Expected Results

      The destination issue has a matching status as the source trigger issue.

      Actual Results

      The rule fails with the following audit log error:

      Transition issue
      Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status)

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [AUTO-383] Transition Issue Action Fails to copy Trigger Issue Status from Team-Managed to Company-Managed Project

            Dylan added a comment -
            Atlassian Update - May 13, 2025

            Hi everyone,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be prioritised. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all cloud users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by commenting back on this issue.

            Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products.

            Atlassian Cloud Engineering

            Dylan added a comment - Atlassian Update - May 13, 2025 Hi everyone, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be prioritised. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all cloud users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by commenting back on this issue. Thank you again for providing valuable feedback to our team, we appreciate your engagement and partnership in helping improve our products. Atlassian Cloud Engineering

            Hello everyone, 

            just wanted to see if there is an update to this ticket? 

            What is expected ETA for this bug to be resolved? 

             

            Cheers,

            Alexey.

            alexey.molodchikov added a comment - Hello everyone,  just wanted to see if there is an update to this ticket?  What is expected ETA for this bug to be resolved?    Cheers, Alexey.

            Hello everyone. 

             

            This issue breaks our integrations between boards and affects every team using Jira automation feature to manage their workflows.

            alexey.molodchikov added a comment - Hello everyone.    This issue breaks our integrations between boards and affects every team using Jira automation feature to manage their workflows.

              Unassigned Unassigned
              4c15e80252ba Chris Boyd (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: