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

Restrict Reporter Field to only users with Create Issues Permission

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

      Problem

      Currently, the Reporter field can be changed from Current User to any browsable user in the system. If you start entering a user that does not have Create Issues permission on that project, it still shows them.

      Assignee already works like this; if you try to type a user that is not assignable, they do not show up.

      Resolution

      Only show users that can create issues in that project, as already exists for Assignee field.

            [JRASERVER-42446] Restrict Reporter Field to only users with Create Issues Permission

            John Smith added a comment -

            Agreed with the above - please fix this.

            John Smith added a comment - Agreed with the above - please fix this.

            Came across this issue within my org too now and this looks more as a severe bug to me rather then an improvement / suggestion.

             

            it allows internal users to mix with external service desk users in projects they should be shielded from.

            Any possible assignee or reporter should be restricted to the project permission.

             

            Deleted Account (Inactive) added a comment - Came across this issue within my org too now and this looks more as a severe bug to me rather then an improvement / suggestion.   it allows internal users to mix with external service desk users in projects they should be shielded from. Any possible assignee or reporter should be restricted to the project permission.  

            Kabelo Mokgoro added a comment - - edited

            This issue has been raise by higher ups in our risk departments as a very pressing matter.
            Has there been any follow up on this feature request?

            I thought maybe i could share our interim solution.
            Set the reporter to read-only (except for certain roles of course).
            Create a custom field (single select list of usernames) where you just add the list of reporters. You then use script runner to set the Reporter field to that field.

            This is long winded (especially as the list of reporters grow) but it solves our immediate problem.

            Kabelo Mokgoro added a comment - - edited This issue has been raise by higher ups in our risk departments as a very pressing matter. Has there been any follow up on this feature request? I thought maybe i could share our interim solution. Set the reporter to read-only (except for certain roles of course). Create a custom field (single select list of usernames) where you just add the list of reporters. You then use script runner to set the Reporter field to that field. This is long winded (especially as the list of reporters grow) but it solves our immediate problem.

            This issue for my company. What is the priority on resolution? 

            Martha Owen added a comment - This issue for my company. What is the priority on resolution? 

            From My point of view this is a bug, because this bypass the "permissions" entered in the corresponding jira project.

            Mesgina Wolday added a comment - From My point of view this is a bug, because this bypass the "permissions" entered in the corresponding jira project.

            I 87th this request.

            Kevin Mowrey added a comment - I 87th this request.

            Hi!

            Yes, that's interesting situation to see external users in internal projects as reporter

            Gonchik Tsymzhitov added a comment - Hi! Yes, that's interesting situation to see external users in internal projects as reporter

            I feel like this is a bug. Any traction here? If assignee go off assignable user permission then reporter should go off of create issue permission. 

            Cameron Birdwell added a comment - I feel like this is a bug. Any traction here? If assignee go off assignable user permission then reporter should go off of create issue permission. 

            How does this issue only have 69 votes so far.... This is an absolutely critical issue that is in desperate need of being fixed. How can anyone be expected to segment their Jira service desks if Reporter shows all users..... 

            Nick Reinhart added a comment - How does this issue only have 69 votes so far.... This is an absolutely critical issue that is in desperate need of being fixed. How can anyone be expected to segment their Jira service desks if Reporter shows all users..... 

            It might help to be more precise on what the ask is:

            1. Restrict Reporter Field to only users with Create Issues Permission OR

            2. Restrict the drop-down in the Reporter Field to display only users with Create Issues Permission

            I think the second case is the one most of us need.

            Enrique Cadalso added a comment - It might help to be more precise on what the ask is: 1. Restrict Reporter Field to only users with Create Issues Permission OR 2. Restrict the drop-down in the Reporter Field to display only users with Create Issues Permission I think the second case is the one most of us need.

              Unassigned Unassigned
              smackie@atlassian.com Shannon S
              Votes:
              197 Vote for this issue
              Watchers:
              124 Start watching this issue

                Created:
                Updated: