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

XMLWordPrintable

    • 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

            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.

            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.

            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.

            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:
              8 Start watching this issue

                Created:
                Updated: