-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Security levels allow JIRA issue visibility to be altered per issue, instead of just per project (as with permission schemes). However, currently security levels can only be set by hand (although a default may apply).
It would be great if we could provide a flexible workflow post-function, which set the security level of an issue based on various configurable criteria. For instance:
- duplicates
-
JRASERVER-9107 Create post-function to set security level
- Gathering Interest
- incorporates
-
JRASERVER-4794 Allow default security level to be set per issue type
- Closed
-
JRASERVER-5276 Allow default issue security level at user/users-group level
- Closed
-
JRASERVER-3838 Allow default issue security level at component level
- Gathering Interest