-
Bug
-
Resolution: Invalid
-
Low
-
None
-
Severity 3 - Minor
-
Jira Software
Issue Summary
Automation rule to copy the security level from Epic to its child will remove the security level from the Epic when a new issue is created.
Steps to Reproduce
- Create a rule to copy the security level of the Epic to the task like this:
- Apply security levels to an epic from a team-managed team (it does not happen in a company-managed one).
- Create an issue and add the epic as its parent. The security levels will be copied.
- Create another issue and add the epic as its parent. The security levels of the parent will be decreased.
- Demonstration
Expected Results
The security level of the epic should be kept and the rule should keep running.
Actual Results
After the second issue, the security levels of the epic are removed.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
AUTO-556 A4J: Automation to be able to set Issue Security level
- Gathering Interest
-
AUTO-750 Ability to update issue restriction (issue security) by automation in team managed project - allow issue security to be inherited from epic as it can be in company-managed projects
- Under Consideration