Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-1131

As a scrum master, I need a way to limit the assignees in the assignee board to just the project's team members, so that I am not overwhlemed with a huge list of users

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.

      Every Jira project has a list of project members, I want my assignee board to be able to be configured to just show those assignees or else there is just too many assignees diplayed on the board to be useful.

      Even better, I'd like to be able to filter the assignee board by roles, so I can create various roles within assignees for "Designers", "QA", etc. and get an idea how those sub teams are allocated (not as important a request as the 1st one)

          Form Name

            [JSWSERVER-1131] As a scrum master, I need a way to limit the assignees in the assignee board to just the project's team members, so that I am not overwhlemed with a huge list of users

            Chris Brookins added a comment -

            Nice!

            On Thu, Aug 19, 2010 at 9:38 PM, Nicholas Muldoon [Atlassian] (JIRA) <

            –
            Chris Brookins : VP Engineering : Acquia : http://acquia.com
            chris@acquia.com : p +1.978.296.5256 : m +1.617.851.2591 : Twitter:
            @chrisbrookins
            Get a free Drupal 7 site at http://DrupalGardens.com

            Chris Brookins added a comment - Nice! On Thu, Aug 19, 2010 at 9:38 PM, Nicholas Muldoon [Atlassian] (JIRA) < – Chris Brookins : VP Engineering : Acquia : http://acquia.com chris@acquia.com : p +1.978.296.5256 : m +1.617.851.2591 : Twitter: @chrisbrookins Get a free Drupal 7 site at http://DrupalGardens.com

            Nicholas Muldoon [Atlassian] added a comment -

            Hello,

            This was resolved in GreenHopper 5.1 when we removed the 75 user limit on the assignees. You can use the Project Roles to limit those people who are assignees so that you do not get every user in your JIRA instance.

            Thank You.

            Regards,
            Nicholas Muldoon

            Nicholas Muldoon [Atlassian] added a comment - Hello, This was resolved in GreenHopper 5.1 when we removed the 75 user limit on the assignees. You can use the Project Roles to limit those people who are assignees so that you do not get every user in your JIRA instance. Thank You. Regards, Nicholas Muldoon

            jon cotter added a comment -

            to address your main point, you should easily be able to create a permission scheme and a jira group that would do exactly what you want.

            for every project i create a group (the assignable users) and in my permission scheme i have this group designated with the Assign Issues permission.

            jon cotter added a comment - to address your main point, you should easily be able to create a permission scheme and a jira group that would do exactly what you want. for every project i create a group (the assignable users) and in my permission scheme i have this group designated with the Assign Issues permission.

            Rich Gay added a comment -

            The role idea would be quite useful.

            Rich Gay added a comment - The role idea would be quite useful.

            Charles Albrecht added a comment -

            My preference would be to limit the display to those assigned to issues in the project (or rather, unresolved issues). This is likely to be somewhat more restrictive than ideal.

            Regardless of whether it's optimal, we will always have extraneous members in project roles who - though they could be assigned taks, will not be and whose presence in the column counts against our 75-user limit and, even when collapsed, clutters the column content.

            Charles Albrecht added a comment - My preference would be to limit the display to those assigned to issues in the project (or rather, unresolved issues). This is likely to be somewhat more restrictive than ideal. Regardless of whether it's optimal, we will always have extraneous members in project roles who - though they could be assigned taks, will not be and whose presence in the column counts against our 75-user limit and, even when collapsed, clutters the column content.

              Unassigned Unassigned
              6d80a6d00f16 Chris Brookins
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: