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

Automation component actions are not updated when Jira component names are changed, e.g. Epic Link field fails if Epic issue types have been renamed

XMLWordPrintable

    • Severity 3 - Minor

      Issue Summary

      When a user updates a Jira component name, it is necessary to update all the rules where that component was being used.

      Steps to Reproduce

      1. Create a Jira component called "mycomponent"
      2. Create an automation rule to set a Jira component to "mycomponent" in an issue
      3. Update the Jira component name to "MyComponent"
      4. Open the rule and check the component name

      Expected Results

      The component name was updated to "MyComponent"

      Actual Results

      The component name is not updated and the rule will start to fail, requiring the user to manually update all the automation components which are using the outdated information

      The below exception is thrown in the Automation audit log:

      Action details:

Edit issue
No fields or field values to edit for issues (could be due to some field values not existing in a given project)

      Workaround

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

            [AUTO-180] Automation component actions are not updated when Jira component names are changed, e.g. Epic Link field fails if Epic issue types have been renamed

            Charlie Gavey added a comment -

            Duplicate of AUTO-468

            Charlie Gavey added a comment - Duplicate of AUTO-468

            NiYunfan added a comment -

            after changing an issue link Outward Description name, it is also not updated in automation rule

            NiYunfan added a comment - after changing an issue link Outward Description name , it is also not updated in automation rule

            Ignacio Pulgar added a comment -

            A similar bug happens when you rename a custom field we had selected in an automation rule:

            It is very surprising that this had not been set to use the custom field id instead of the field name.

            Please fix this!

            Ignacio Pulgar added a comment - A similar bug happens when you rename a custom field we had selected in an automation rule: It is very surprising that this had not been set to use the custom field id instead of the field name. Please fix this!

            bharvell added a comment -

            I had a similar issue where a custom field value for a select option changed and we had to update the rule with the new select value as well.

            bharvell added a comment - I had a similar issue where a custom field value for a select option changed and we had to update the rule with the new select value as well.

              Unassigned Unassigned
              bd0e47de2684 Yuri Moura (Inactive)
              Affected customers:
              16 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: