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

Group the Assignee list by group, security level or project roles

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

      Hi
      I see it as a great advantages if the assignee list could be grouped. E.g. by groups, security level or project roles.
      I use jira to manage issues or questions towards several companies (splitted into different sequrity levels). For each company there is several jira-users. When I create an issue, or should assign a jira issue, it would be a great advantage for me to have the assignee list grouped.

      Assignee:
      Company_A

      • user 1
      • user 2
      • user 3
        Companty_B
      • user 4
      • user 5

      I have serached for a plugins for this functionality, but havne't found any

      If this will be implemented, as I see it, this should be setting pr. project. Project admin should be able to choose if th assignee list should be grouped by group, security level, project roles or not grouped.

      An other solution would be to add security level to the first screen when creating an issue (together with project and issue type).
      Then the assignee list on the 2nd screen should only contain users according to the security level set for the issue.

            [JRASERVER-16557] Group the Assignee list by group, security level or project roles

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Roy Krishna and Josh Devenny
            JIRA Product Management

            Roy Krishna (Inactive) added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Roy Krishna and Josh Devenny JIRA Product Management

              Unassigned Unassigned
              0372561f68c4 Rune Waage
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: