-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
all our projects have the same set of permissions, however, we have to implement a distinct permission scheme for each project, because we have "project groups" where only users assigned to that project can edit/schedule/assign/assignable/resolve issues.
this means creating a separate permission scheme for each project, copying another, and removing one set of groups and adding another.
if 'project group' were an option on the Add New Permission page, this would greatly simplify our administration. one way to make this work would be that if project-group were seleted, anyone in a group with the SAME NAME as the project would be given that permission.
alternately, the database structure could be modified to allow assigning one (add fk) or more than one (new table), but this would probably be a lot more work.
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Closed
[JRACLOUD-2414] add "project group" feature to ease permissions management
| Workflow | Original: JAC Suggestion Workflow [ 3155846 ] | New: JAC Suggestion Workflow 3 [ 3656860 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2349918 ] | New: JAC Suggestion Workflow [ 3155846 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Component/s | New: Project Administration - Issue type, fields and Other [ 53196 ] | |
| Component/s | Original: Project Administration [ 46539 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2108630 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2349918 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2071854 ] | New: JIRA Bug Workflow w Kanban v6 [ 2108630 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1861652 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2071854 ] |
| Description |
Original:
all our projects have the same set of permissions, however, we have to implement a distinct permission scheme for each project, because we have "project groups" where only users assigned to that project can edit/schedule/assign/assignable/resolve issues. this means creating a separate permission scheme for each project, copying another, and removing one set of groups and adding another. if 'project group' were an option on the Add New Permission page, this would greatly simplify our administration. one way to make this work would be that if project-group were seleted, anyone in a group with the SAME NAME as the project would be given that permission. alternately, the database structure could be modified to allow assigning one (add fk) or more than one (new table), but this would probably be a lot more work. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Cloud*. Using *JIRA Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRASERVER-2414]. {panel} all our projects have the same set of permissions, however, we have to implement a distinct permission scheme for each project, because we have "project groups" where only users assigned to that project can edit/schedule/assign/assignable/resolve issues. this means creating a separate permission scheme for each project, copying another, and removing one set of groups and adding another. if 'project group' were an option on the Add New Permission page, this would greatly simplify our administration. one way to make this work would be that if project-group were seleted, anyone in a group with the SAME NAME as the project would be given that permission. alternately, the database structure could be modified to allow assigning one (add fk) or more than one (new table), but this would probably be a lot more work. |
| Link |
New:
This issue is related to |
| Link | New: This issue is related to JSWCLOUD-2849 [ JSWCLOUD-2849 ] |
| Project Import | New: Sat Apr 01 19:36:47 UTC 2017 [ 1491075407146 ] |
