-
Bug
-
Resolution: Fixed
-
Low
-
3.12
-
3.12
-
When you move a subtask from an Issue Type where Security Level is a hidden field, to one where Security Level is no longer hidden,
the system can mistakenly ask the User for a new Security Level.
This is only a minor issue, as then the subtask will not actually take on the chosen value - it will keep the Security Level of the parent.
In order to replicate this you may need to have a project with a Default Security Level.
- is related to
-
JRASERVER-14035 When security level appears as a field on Workflow transitions, then it should not be editable for subtasks.
- Closed