-
Bug
-
Resolution: Duplicate
-
Low
-
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
- Create a Jira component called "mycomponent"
- Create an automation rule to set a Jira component to "mycomponent" in an issue
- Update the Jira component name to "MyComponent"
- 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
- duplicates
-
AUTO-468 Support for field IDs instead of just field names in Automation, so rules don't break when fields are renamed, and to support custom fields with the same name
- Gathering Interest