-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Concerning permission scheme administration, we've got a proposal to relieve some stress of a jira admin 
Currently it's possible to copy an existing scheme. However, the new scheme is called "copy of ..." and contains the exact same groups as its ancestor (the original). Usually we want to copy a scheme but we want the same "kind" of groups in the new scheme but they have different names. An example.
Suppose we've got a project called XXXX with its associated permission scheme XXXX.
Permission scheme XXXX contains the following groups:
- XXXX-users
- XXXX-developers
- XXXX-administrators
We create a new project YYYY and want permission scheme YYYY. For this group YYYY we want the same groups as in scheme XXXX with different but analogous names.
Scheme YYYY
- YYYY-users
- YYYY-developers
- YYYY-administrators
So, actually, these were a lot of words to ask only for a possibility to do a "find/replace" when copying a permission scheme. Automatically creating the new groups of the new scheme if they don't exist yet is yet another small thing to make the life of an admin a little less painful 
- duplicates
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
-
- Closed
-
- Closed
[JRASERVER-2018] permission scheme administration improvements
| Workflow | Original: JAC Suggestion Workflow [ 3054350 ] | New: JAC Suggestion Workflow 3 [ 3684143 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2618761 ] | New: JAC Suggestion Workflow [ 3054350 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2589728 ] | New: Confluence Workflow - Public Facing v4 [ 2618761 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2346972 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2589728 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2113708 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2346972 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091471 ] | New: JIRA Bug Workflow w Kanban v6 [ 2113708 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 889816 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091471 ] |
| Description |
Original:
Concerning permission scheme administration, we've got a proposal to relieve some stress of a jira admin ;-)
Currently it's possible to copy an existing scheme. However, the new scheme is called "copy of ..." and contains the exact same groups as its ancestor (the original). Usually we want to copy a scheme but we want the same "kind" of groups in the new scheme but they have different names. An example. Suppose we've got a project called XXXX with its associated permission scheme XXXX. Permission scheme XXXX contains the following groups: - XXXX-users - XXXX-developers - XXXX-administrators We create a new project YYYY and want permission scheme YYYY. For this group YYYY we want the same groups as in scheme XXXX with different but analogous names. Scheme YYYY - YYYY-users - YYYY-developers - YYYY-administrators So, actually, these were a lot of words to ask only for a possibility to do a "find/replace" when copying a permission scheme. Automatically creating the new groups of the new scheme if they don't exist yet is yet another small thing to make the life of an admin a little less painful :-) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-2018]. {panel} Concerning permission scheme administration, we've got a proposal to relieve some stress of a jira admin ;-) Currently it's possible to copy an existing scheme. However, the new scheme is called "copy of ..." and contains the exact same groups as its ancestor (the original). Usually we want to copy a scheme but we want the same "kind" of groups in the new scheme but they have different names. An example. Suppose we've got a project called XXXX with its associated permission scheme XXXX. Permission scheme XXXX contains the following groups: - XXXX-users - XXXX-developers - XXXX-administrators We create a new project YYYY and want permission scheme YYYY. For this group YYYY we want the same groups as in scheme XXXX with different but analogous names. Scheme YYYY - YYYY-users - YYYY-developers - YYYY-administrators So, actually, these were a lot of words to ask only for a possibility to do a "find/replace" when copying a permission scheme. Automatically creating the new groups of the new scheme if they don't exist yet is yet another small thing to make the life of an admin a little less painful :-) |
| Link |
New:
This issue relates to |
| Component/s | New: Project Administration - Permissions [ 10321 ] | |
| Component/s | Original: Administration [Deprecated] [ 10271 ] |
