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

Limit user picker to members of certain groups / roles

XMLWordPrintable

    • 30
    • 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.

      Atlassian Status as of 30th January 2014

      Hi everyone,

      Thanks so much for your votes and comments on this feature request.

      Good news! The upcoming release of JIRA 6.2 (planned for the first quarter of calendar year 2014) will introduce the "limited user picker" functionality for single user pickers based on custom fields. The limiting will be configurable based on rules, each rule defining a project role or group from which the users will be displayed. In case of multiple rules, the final list will be the union of lists as defined by individual rules. Rules will be defined within the context of the custom field configuration: therefore they will be separate for each combination of project and issue type.
      As mentioned above, the rules definition will be applicable to all user picker custom fields, and as a consequence will currently not cover the scenarios for:

      • the user picker for system fields of reporter and assignee (JRA-36896)
      • the multiple user picker (JRA-36833)

      Thanks for your patience and we hope you appreciate our open approach to feature requests.

      Cheers,
      Bartek
      JIRA Product Management
      bartek (at) atlassian (dot) com

      Original request description

      As JIRA user and administrator I want to be able to use a user picker field in such a way that only users from selected groups or roles ale allowed for selection. This way I will be able to limit the choice (which is important in large scale deployments), but also assure that only users who are expected to provide actionable follow up are selected (for instance in case of bugs, these should be only developers and QA, and not sales engineers).

        1. Unbenannt.png
          Unbenannt.png
          38 kB
        2. Ν. Γρέτος Screenshot-1.png
          Ν. Γρέτος Screenshot-1.png
          196 kB

            [JRASERVER-7659] Limit user picker to members of certain groups / roles

            Filip Nowak made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 752127 ]
            Joshua Wilson (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 705972 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3058434 ] New: JAC Suggestion Workflow 3 [ 3693989 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Isaac.nl made changes -
            Link New: This issue relates to JRASERVER-40283 [ JRASERVER-40283 ]
            set-jac-bot made changes -
            Link New: This issue details JRASERVER-23902 [ JRASERVER-23902 ]
            Ilya Zinoviev (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-7659].
              {panel}

            {panel:title=Atlassian Status as of 30th January 2014|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
            Hi everyone,

            Thanks so much for your votes and comments on this feature request.

            Good news! The upcoming release of JIRA 6.2 (planned for the first quarter of calendar year 2014) will introduce the "limited user picker" functionality for single user pickers based on custom fields. The limiting will be configurable based on rules, each rule defining a project role or group from which the users will be displayed. In case of multiple rules, the final list will be the union of lists as defined by individual rules. Rules will be defined within the context of the custom field configuration: therefore they will be separate for each combination of project and issue type.
            As mentioned above, the rules definition will be ap
            plicable to all user picker custom fields, and as a consequence will currently *not* cover the scenarios for:
            * the user picker for system fields of reporter and assignee (JRA-36896)
            * the multiple user picker (JRA-36833)

            Thanks for your patience and we hope you appreciate our open approach to feature requests.

            Cheers,
            Bartek
            JIRA Product Management
            bartek (at) atlassian (dot) com
            {panel}
            *Original request description*

            As JIRA user and administrator I want to be able to use a user picker field in such a way that only users from selected groups or roles ale allowed for selection. This way I will be able to limit the choice (which is important in large scale deployments), but also assure that only users who are expected to provide actionable follow up are selected (for instance in case of bugs, these should be only developers and QA, and not sales engineers).             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-7659].
              {panel}

            {panel:title=Atlassian Status as of 30th January 2014|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}
            Hi everyone,

            Thanks so much for your votes and comments on this feature request.

            Good news! The upcoming release of JIRA 6.2 (planned for the first quarter of calendar year 2014) will introduce the "limited user picker" functionality for single user pickers based on custom fields. The limiting will be configurable based on rules, each rule defining a project role or group from which the users will be displayed. In case of multiple rules, the final list will be the union of lists as defined by individual rules. Rules will be defined within the context of the custom field configuration: therefore they will be separate for each combination of project and issue type.
            As mentioned above, the rules definition will be applicable to all user picker custom fields, and as a consequence will currently *not* cover the scenarios for:
            * the user picker for system fields of reporter and assignee (JRA-36896)
            * the multiple user picker (JRA-36833)

            Thanks for your patience and we hope you appreciate our open approach to feature requests.

            Cheers,
            Bartek
            JIRA Product Management
            bartek (at) atlassian (dot) com
            {panel}
            *Original request description*

            As JIRA user and administrator I want to be able to use a user picker field in such a way that only users from selected groups or roles ale allowed for selection. This way I will be able to limit the choice (which is important in large scale deployments), but also assure that only users who are expected to provide actionable follow up are selected (for instance in case of bugs, these should be only developers and QA, and not sales engineers).
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2619261 ] New: JAC Suggestion Workflow [ 3058434 ]
            Tomasz Kanafa made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 363635 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2592633 ] New: Confluence Workflow - Public Facing v4 [ 2619261 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2360162 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2592633 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              e5e14e4e5311 Rémy Mouton
              Votes:
              329 Vote for this issue
              Watchers:
              245 Start watching this issue

                Created:
                Updated:
                Resolved: