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

Remove ability to add portal user as reporter

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 1
    • 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 an instance has Service Desk, users can add customer portal-only users as reporters of tickets in Software and Core projects. This can be problematic, and can cause confusion among other users, as portal-users should be completely restricted to Service Desk projects. If possible, I believe we should remove that ability from the product.

          Form Name

            [JRASERVER-60427] Remove ability to add portal user as reporter

            Gosia Kowalska added a comment -
            Atlassian Update – 29 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 29 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

            William Byrne added a comment -

            This one is killing us because our team is constantly accidentally assigning the report to users that are service desk portal-only users to JIRA software issues. When you have many users it's hard to keep track of who is portal-only and who is a software user. When they get assigned as the reporter the issue communication essentially gets lost because that portal user won't get any of the notifications.

            William Byrne added a comment - This one is killing us because our team is constantly accidentally assigning the report to users that are service desk portal-only users to JIRA software issues. When you have many users it's hard to keep track of who is portal-only and who is a software user. When they get assigned as the reporter the issue communication essentially gets lost because that portal user won't get any of the notifications.

              Unassigned Unassigned
              efranklin Eric Franklin (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: