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

Automation rule can't create a new issue if components are missing in the target project

XMLWordPrintable

    • Severity 2 - Major
    • Jira Software, Jira Service Management

      Issue Summary

      This is reproducible on the cloud: yes

      Steps to Reproduce

      1. Configure an automation rule to create a new issue in a different project.
      2. The rule should also copy components from the trigger issue to the created issue with the option "Add to existing values" checked
      3. Run the rule for a scenario where some of the components on the trigger issue's project are not present in the created issue's project.

      Expected Results

      The rule should be able to create an issue in the target project even if some components are not found.

      It should skip the components that were not found in the target project and add the components that were found.

      Actual Results

      The rule does not create a new issue if some components are not found and shows the below error.

      Workaround

      None

        1. Screenshot 2024-06-17 at 4.22.32 PM.png
          Screenshot 2024-06-17 at 4.22.32 PM.png
          176 kB
        2. Screenshot 2024-06-17 at 4.28.22 PM.png
          Screenshot 2024-06-17 at 4.28.22 PM.png
          81 kB
        3. Screenshot 2024-06-17 at 4.28.33 PM.png
          Screenshot 2024-06-17 at 4.28.33 PM.png
          58 kB

            [AUTO-1326] Automation rule can't create a new issue if components are missing in the target project

            Bill Sheboy added a comment -

            Greetings!

            Please document / describe the "fix" applied.  For example, are the "not found" components skipped, added to the destination project, or something else?

            IMHO, the root cause of this is the error message was too vague.  The existing behavior of not creating the issue seemed correct.

            Thanks!

            Bill Sheboy added a comment - Greetings! Please document / describe the "fix" applied.   For example, are the "not found" components skipped, added to the destination project, or something else? IMHO, the root cause of this is the error message was too vague.  The existing behavior of not creating the issue seemed correct. Thanks!

              Unassigned Unassigned
              4e832f0f7b6e Bhavin Rathod
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: