Have Security Levels set up and all work properly. When creating a Sub-Task for a Parent issue with a Security Level in effect, the Sub-Task is still viewable by users that do not have permission to view the Security Level of the Parent Issue.
Users cannot view the Parent Issue, but they are able to view the Sub-task which is suppossed to inherit the Security Level from it's parent task.
The system does not allow for the editing of the Security Level in the Sub-Task. When you try it tells you that the Sub-Task inherits the Parent Issue's Security Level.
Anyone have suggestions on what might not be set up correctly that would allow this situation?
I tried to replicate this issue in a test instance but couldn't reproduce the problem. I noticed that the label is OnDemand.
Please raise a support ticket at https://support.atlassian.com so that we can look into this case further.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs