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

Limit "Assign To" lists to real project 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      If a user has no right to see a project (no Browse Project permission) than she/he shouldn't be be choosed in the assignable users list (in the 'assign issue screen').

      If we set the "Assignable User" permission to some project roles (for example: Developers and some custom ones) and we put some users&user groups to these roles, but some of these users don't have the permission to see the project (no Browse Projects permission for them)... we still can choose these users in the assignable user list in the 'assign issue screen'.

            [JRASERVER-23649] Limit "Assign To" lists to real project users

            Kerrod Williams (Inactive) added a comment -

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.
            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Deleted Account (Inactive) added a comment -

            Maybe JRA-7467 is not very well written, but I believe it is the same issue.

            Deleted Account (Inactive) added a comment - Maybe JRA-7467 is not very well written, but I believe it is the same issue.

              Unassigned Unassigned
              31a956cd76ce Bódis Tamás
              Votes:
              6 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: