Le lundi 17 août 2015, Kanstantsin Shautsou <[email protected]> a écrit :
> > > On Monday, August 17, 2015 at 1:36:48 PM UTC+3, Arnaud Héritier wrote: >> >> Hi, >> >> I missed this discussion and found it by looking some details about the >> process to manage security issues. >> I'm not sure if a need was really defined but to restrict the >> visibility of an issue (or only a comment) we can just define in Jira a >> "security level" to apply on issues. >> A security level is something you define on top of the project/issues >> permissions to restrict the visibility of an issue or comment >> >> Arnaud >> > Does it require right configured groups in jira? > Jira is using a RBAC like model (roles - groups users) For each project you have various roles in which you add user(s) and/or group(s) In permissions schemes you define for each permission (browse project, open issue, ...) which project role(s), group(s) and/or user(s) are allowed In security schemes you define which project role(s), group(s) and/or user(s) are allowed to browse an issue or a comment. The security scheme has a default configuration and is supposed to restrict the visibility provided by the permission "browse project" (perhaps "view comment", I don't remember if it has specific permission). The ability to change the security level is a distinct permission this you can give this ability to a subset of people. -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--L1cZ3Gem5K37C-6yB_hj8y_hDkcyJstfVQemk-PcYxg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
