Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2414

add "project group" feature to ease permissions management

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

            [JRASERVER-2414] add "project group" feature to ease permissions management

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3046579 ] New: JAC Suggestion Workflow 3 [ 3671707 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2605708 ] New: JAC Suggestion Workflow [ 3046579 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2556970 ] New: Confluence Workflow - Public Facing v4 [ 2605708 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2346973 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2556970 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2113713 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2346973 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091495 ] New: JIRA Bug Workflow w Kanban v6 [ 2113713 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 879727 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091495 ]
            jonah (Inactive) made changes -
            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 Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-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.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-2414 [ JRACLOUD-2414 ]

            Rizwan Akbar added a comment - - edited

            Dear Jira Team,

            I also about to report a suggestion related to it. There MUST be a concept of Teams with designation and expertise in Jira so that we can better management the users and teams. Also, there should be a permission type, "Team Members". If someone selected this option in Permission Schemes, anyone in the team can access that functionality.

            We have 9 projects and if we do not want the team to see each other project, we have to create 9 Permission Schemes. If you implement Team Members and a permission type then one can manage multiple projects with one Permission Scheme.

            Best Regards,
            Rizwan Akbar

            Rizwan Akbar added a comment - - edited Dear Jira Team, I also about to report a suggestion related to it. There MUST be a concept of Teams with designation and expertise in Jira so that we can better management the users and teams. Also, there should be a permission type, "Team Members". If someone selected this option in Permission Schemes, anyone in the team can access that functionality. We have 9 projects and if we do not want the team to see each other project, we have to create 9 Permission Schemes. If you implement Team Members and a permission type then one can manage multiple projects with one Permission Scheme. Best Regards, Rizwan Akbar

              Unassigned Unassigned
              d32fc554e6cd Tim Dawson
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: