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

          Form Name

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

            n.schelfaut added a comment -

            I would like to see this in Jira Cloud too. Missing it there.

            n.schelfaut added a comment - I would like to see this in Jira Cloud too. Missing it there.

            David Holshouser added a comment - - edited

            How can I use user roles to populate issue fields?

            I mean this in an automatic sort of way. Eg on issue creation, I'd like to set my SQA or Developer to the Project Role that has been configured.

            I've looked in issue workflow transition post functions and custom field default values and neither support user roles.

            Now that this issue added support for user roles, I'd like to use these roles in my issues to populate fields.

            David Holshouser added a comment - - edited How can I use user roles to populate issue fields? I mean this in an automatic sort of way. Eg on issue creation, I'd like to set my SQA or Developer to the Project Role that has been configured. I've looked in issue workflow transition post functions and custom field default values and neither support user roles. Now that this issue added support for user roles, I'd like to use these roles in my issues to populate fields.

            roniz added a comment -

            david.skreiner- I am currently using JIRA version 6.4.12- but I still cannot find the "User Filtering" option after creating a "User Picker (single user) field" and trying to configure it- Do you know why?

            roniz added a comment - david.skreiner - I am currently using JIRA version 6.4.12- but I still cannot find the "User Filtering" option after creating a "User Picker (single user) field" and trying to configure it- Do you know why?

            raju singh added a comment -

            I guess, we should have something like this:

            1. Have a custom field - Group picker. This should be restricted project wise.
            2. Have a custom field - User picker. Based on the Group selected, User field content should change.

            When can we get this feature enabled?

            raju

            raju singh added a comment - I guess, we should have something like this: Have a custom field - Group picker. This should be restricted project wise. Have a custom field - User picker. Based on the Group selected, User field content should change. When can we get this feature enabled? raju

            Cory Burns added a comment -

            Is there a way to do this with Groups as well? currently I can do this with user no problem I want to use a custom field that when assigning tickets to groups, but don't want those tickets assigned to say the admin group

            Cory Burns added a comment - Is there a way to do this with Groups as well? currently I can do this with user no problem I want to use a custom field that when assigning tickets to groups, but don't want those tickets assigned to say the admin group

            Fabrizio Galletti added a comment -

            uh thanks

            Fabrizio Galletti added a comment - uh thanks

            David Skreiner added a comment - - edited

            The feature is there (I just found it in JIRA 6.4), but quite well-hidden. It doesn't show up when creating a new field, only when configuring an existing field.

            1. Open "Custom fields"
            2. Click "+Add Custom Field"
            3. Create a "User Picker (single user) field.
            4. After creating your field, find it on the "Custom Fields" screen, and choose "Configure" from the menu icon on the right.
            You should now see a "User Filtering" option. This allows you to add a filter for project role or group.

            David Skreiner added a comment - - edited The feature is there (I just found it in JIRA 6.4), but quite well-hidden. It doesn't show up when creating a new field, only when configuring an existing field. 1. Open "Custom fields" 2. Click "+Add Custom Field" 3. Create a "User Picker (single user) field. 4. After creating your field, find it on the "Custom Fields" screen, and choose "Configure" from the menu icon on the right. You should now see a "User Filtering" option. This allows you to add a filter for project role or group.

            Jan Szczepanski added a comment -

            Hi,

            we have Q3/2015 and this feature still not available. Any suggestions when it will be released?

            Regards,
            Jan

            Jan Szczepanski added a comment - Hi, we have Q3/2015 and this feature still not available. Any suggestions when it will be released? Regards, Jan

            Chas Berndt added a comment -

            I'm on 6.2.4 and I don't see this as an option when trying to create a custom field.

            Chas Berndt added a comment - I'm on 6.2.4 and I don't see this as an option when trying to create a custom field.

            ZehuaA added a comment -

            Hi Jennifer,

            Thanks for the quick reply. I've confirmed with the Service Desk team that this is indeed a bug. It's being tracked in https://jira.atlassian.com/browse/JSD-590. You might want to watch it.

            Cheers,

            Zehua

            ZehuaA added a comment - Hi Jennifer, Thanks for the quick reply. I've confirmed with the Service Desk team that this is indeed a bug. It's being tracked in https://jira.atlassian.com/browse/JSD-590 . You might want to watch it. Cheers, Zehua

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

                Created:
                Updated:
                Resolved: