-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
The idea is to allow a scheme (permission, notification etc) to be defined in terms of another scheme, and extend it in some direction. Changes to the underlying scheme would take effect in all 'extending' schemes immediately.
> More important, however, whould be the possibility to let a project "inherit" the permission scheme of its super project (if there is a super project) and to let a super project inherit the permission scheme of a project group (if there is such a group). So, we're actually looking for permission scheme inheritance in the project group/super project/subproject hierarchy. Of course it should be possible to override the inheritance and specify a custom scheme anyway.
- relates to
-
JRACLOUD-8895 Scheme inheritance: define schemes in terms of other schemes, to factor out commonalities
- Closed
-
JRASERVER-1566 Assign Multiple Notification Schemes to a Project
- Closed
-
JRASERVER-2816 Role based permission schemes (eg. 'grant BROWSE to ${project}-users')
- Closed
- mentioned in
-
Page Failed to load
[JRASERVER-8895] Scheme inheritance: define schemes in terms of other schemes, to factor out commonalities
Workflow | Original: JAC Suggestion Workflow [ 3052250 ] | New: JAC Suggestion Workflow 3 [ 3680952 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2615472 ] | New: JAC Suggestion Workflow [ 3052250 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2582160 ] | New: Confluence Workflow - Public Facing v4 [ 2615472 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2360205 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2582160 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2127688 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2360205 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2090401 ] | New: JIRA Bug Workflow w Kanban v6 [ 2127688 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 889841 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2090401 ] |
Description |
Original:
The idea is to allow a scheme (permission, notification etc) to be defined in terms of another scheme, and extend it in some direction. Changes to the underlying scheme would take effect in all 'extending' schemes immediately.
> More important, however, whould be the possibility to let a project "inherit" the permission scheme of its super project (if there is a super project) and to let a super project inherit the permission scheme of a project group (if there is such a group). So, we're actually looking for permission scheme inheritance in the project group/super project/subproject hierarchy. Of course it should be possible to override the inheritance and specify a custom scheme anyway. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-8895]. {panel} The idea is to allow a scheme (permission, notification etc) to be defined in terms of another scheme, and extend it in some direction. Changes to the underlying scheme would take effect in all 'extending' schemes immediately. > More important, however, whould be the possibility to let a project "inherit" the permission scheme of its super project (if there is a super project) and to let a super project inherit the permission scheme of a project group (if there is such a group). So, we're actually looking for permission scheme inheritance in the project group/super project/subproject hierarchy. Of course it should be possible to override the inheritance and specify a custom scheme anyway. |
Link |
New:
This issue relates to |
Component/s | New: Project Administration - Others [ 43422 ] | |
Component/s | Original: Project Management [Deprecated] [ 11643 ] |