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

Using A4J to clone issues from a team-managed project into another does not automatically map issue types

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      Automation for Jira does not automatically map issue types when cloning issues among Team-managed projects.

      Steps to Reproduce

      1. Create an automation rule (can be triggered by JQL) that clones issues from one team-managed project into another
      2. Run the automation.

      Expected Results

      Actual Results

      Note that the issue is also reproducible when cloning a company-managed project onto another. The automation rule associates the issue type with a Team-Managed issue type instead

      Also please note that the issue is intermittent. 

      Workaround

      A possible workaround would be to create a new issue using the Create issue action instead of cloning the issue and copying the field values from the trigger issue.

              Unassigned Unassigned
              ff0d32d1429f Roberto Amorim (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: