• 7
    • 6
    • 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 Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Right now it appears that the Assign Permission is all or nothing.

      We would like force the "Assign To" functionality to limit the list of users to only be in the user group defined.
      Thus, if the workflow step defined assigning to a developer, the user list will only display the list of developers. If the workflow step is to assign to a QA Engineer, the QA Engineer would only have assign-permission to assign to another QA Engineer.

      If would be even better if we can configure based on the user's group to specify which group of users should show. For example:-
      User group A able to assign ticket to only user in group A
      User group B able to assign ticket to users from group A and B

            [JRASERVER-6126] Limit "Assign To" list to specific user group

            Hi Guys,

            you may use User group picker to restrict a user picker to a specific or dynamic group or role. It's free.

            To set the assignee, reporter or any other system or custom field you may use JJUPIN and it's Simple Issue Language.
            Setting a value to a custom or standard field requires one line of code:

            Some SIL code
            assignee="admin";
            customfield_10000=customfield_10001-1;
            

            Here are some of examples:
            http://confluence.kepler-rominfo.com/display/JJUP20/Simple+Issue+Language+Usage

            Give it a try here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin
            or here http://jira-plugins.kepler-rominfo.com/x/product/id/3

            Here is how you create a condition, validator or post-function: http://confluence.kepler-rominfo.com/display/JJUP20/Writing+Validators%2C+Postfunctions+and+Conditions

            Florin Haszler (Alten Kepler) added a comment - Hi Guys, you may use User group picker to restrict a user picker to a specific or dynamic group or role. It's free. To set the assignee, reporter or any other system or custom field you may use JJUPIN and it's Simple Issue Language. Setting a value to a custom or standard field requires one line of code: Some SIL code assignee= "admin" ; customfield_10000=customfield_10001-1; Here are some of examples: http://confluence.kepler-rominfo.com/display/JJUP20/Simple+Issue+Language+Usage Give it a try here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin or here http://jira-plugins.kepler-rominfo.com/x/product/id/3 Here is how you create a condition, validator or post-function: http://confluence.kepler-rominfo.com/display/JJUP20/Writing+Validators%2C+Postfunctions+and+Conditions

            Hi Jørgen and others

            Have a look on User By Workflow Step ... It may amswer to your need.

            Vincent

            Vincent Thoulé added a comment - Hi Jørgen and others Have a look on User By Workflow Step ... It may amswer to your need. Vincent

            Alex and Nitish, maybe I misunderstand this issue but your proposal for a solution breaks in my case which is using JIRA for customer communication. What I wan't from this is to limit the list of users that the customer can assign an issue to. You wouldn't want the customer to assign an issue to a developer. The logical thing for me would be to put the customer (and all other interested parties) in the users project role and then let project users only be able to assign issues to the project leader.

            Deleted Account (Inactive) added a comment - Alex and Nitish, maybe I misunderstand this issue but your proposal for a solution breaks in my case which is using JIRA for customer communication. What I wan't from this is to limit the list of users that the customer can assign an issue to. You wouldn't want the customer to assign an issue to a developer. The logical thing for me would be to put the customer (and all other interested parties) in the users project role and then let project users only be able to assign issues to the project leader.

            The best work around according to me,for this would be:
            Edit the Permission schemes: Assignable users ->Project Role:Developers (which is default:jira-developer)

            Then each Project Leader could add users to Developers role for his project.

            Hence for any issue, the "assign to" list will only show those users which are "developers" for that project.

            Nitish Mahajan added a comment - The best work around according to me,for this would be: Edit the Permission schemes: Assignable users ->Project Role:Developers (which is default:jira-developer) Then each Project Leader could add users to Developers role for his project. Hence for any issue, the "assign to" list will only show those users which are "developers" for that project.

            Can this be achieved via creating a group with the list of approved assignees and then create a Permission Schemes and use the group under "Assignable User" ?

            Alex Tabrizi added a comment - Can this be achieved via creating a group with the list of approved assignees and then create a Permission Schemes and use the group under "Assignable User" ?

            It would be great if we could name a few jira-users as Project Role- Developers and then in the assign to list only those developers are shown.

            Nitish Mahajan added a comment - It would be great if we could name a few jira-users as Project Role- Developers and then in the assign to list only those developers are shown.

            We also need this functions. Currently all users apear in the dropdown. This creates problems when the wrong person (role) is selected and it would be great to be able to filter the displayed list to only the applicable group (say developers).

            Francois Botha added a comment - We also need this functions. Currently all users apear in the dropdown. This creates problems when the wrong person (role) is selected and it would be great to be able to filter the displayed list to only the applicable group (say developers).

            Nick Bence added a comment -

            This would be useful. Can the plugin be added to the plugin exchange, with compatibility grid.

            Nick Bence added a comment - This would be useful. Can the plugin be added to the plugin exchange, with compatibility grid.

            On the plug-in page they say: "broken and deprecated."

            Gunnar Wagenknecht added a comment - On the plug-in page they say: "broken and deprecated."

            AntonA added a comment -

            We are considering including this functionality in a future version of JIRA. As this issue has not been scheduled yet, unfortunately I cannot provide an accurate time line for its implementation.

            The plugin is labeled a 'hack' as it relies on manually adding properties to step definitions in the workflow. When we include this functionality in JIRA we might change the way it works.

            The source to the plugin can be found here:
            http://repository.atlassian.com/atlassian-jira-workflowbasedpermissions-plugin/distributions/

            So if you like you can customise it to your needs.

            Thanks,
            Anton

            AntonA added a comment - We are considering including this functionality in a future version of JIRA. As this issue has not been scheduled yet, unfortunately I cannot provide an accurate time line for its implementation. The plugin is labeled a 'hack' as it relies on manually adding properties to step definitions in the workflow. When we include this functionality in JIRA we might change the way it works. The source to the plugin can be found here: http://repository.atlassian.com/atlassian-jira-workflowbasedpermissions-plugin/distributions/ So if you like you can customise it to your needs. Thanks, Anton

              Unassigned Unassigned
              9e50ff64ea6d Joshua Standing
              Votes:
              138 Vote for this issue
              Watchers:
              54 Start watching this issue

                Created:
                Updated: