Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-81318

Hide or filter out portal only users (JSM Customers) who don't have Jira application access to appear on assignee, reporters, project lead and project roles list

    • 916
    • 158
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      I know this sounds like a duplicate of JRA-7659, but that one is about the perfect generic solution to the user picker problem.

      This issue here is about a basic (small) but necessary improvement: don't show users who don't have access to Jira or have the ability to filter these accounts out.

      Most people will benefit from it, since almost any jira instance will have some old users accounts floating around, which have no access to the instance anymore (because they left the company, or...). It is even possible to select Portal Only customer as a reporter and project roles for non-Jira Service Desk issues.

      Steps to replicate

      Scenario 1

      1. Invite User as a Portal Only customer
      2. Go to Project Settings
      3. Click on People and add People.
      4. Type a Portal only customer and add any roles.
      5. "GG" audit Log

      Scenario 2

      1. Invite User to your instance (and revoke access to Jira) or as a Portal Only customer
      2. Create an issue
      3. Select the User who doesn't have Jira access or Portal Only customer as the reporter

      Expected

      • User who doesn't have Jira access or Portal Only customer isn't visible through the reporter/user picker list
      • User who doesn't have Jira access or Portal Only customer can't be assign to Project Roles

      Actual Result

      • User who doesn't have Jira access or Portal Only customer can be added on Project Roles
      • They can also be assigned to any Roles
      • Audit Log show the portal only customers ID Starting with "qm:..."
      • User who doesn't have Jira access or Portal Only customer able to be selected as the reporter (even for non-Jira Service Desk issues)

      Suggestion

      Hide or Filter out the Portal Only Customer/User without access from appearing on projects where they shouldn't be.

       

            [JRACLOUD-81318] Hide or filter out portal only users (JSM Customers) who don't have Jira application access to appear on assignee, reporters, project lead and project roles list

            Thank you for bringing this up ad6a7dfa16ba 

            I have now removed the workaround that was added, because it was specific to a particular customer's case and would not serve as a workaround to all for this specific issue.

            Bhaargavi Natarajan added a comment - Thank you for bringing this up ad6a7dfa16ba   I have now removed the workaround that was added, because it was specific to a particular customer's case and would not serve as a workaround to all for this specific issue.

            Majken Longlade added a comment -

            I have real concerns about that workaround that was just added by Zee. Unless I'm missing something the workaround is the equivalent to "don't have customers", which isn't a workaround at all. I also think the article is poorly written and the workaround is not described sufficiently, that some people may just try this thinking they're deleting customers from a place that just affects user fields and not from their instance entirely!

            Majken Longlade added a comment - I have real concerns about that workaround that was just added by Zee. Unless I'm missing something the workaround is the equivalent to "don't have customers", which isn't a workaround at all. I also think the article is poorly written and the workaround is not described sufficiently, that some people may just try this thinking they're deleting customers from a place that just affects user fields and not from their instance entirely!

            Jenn McGugan added a comment - - edited

            While I'd like to limit the assignee user picker to only those who work the back end of the tickets, both the reporter field and the requested participants fields for our system need to see and be able to choose from the portal only customers. If you can make it so we can choose which fields are limited by specific criteria, which would be unique for each field, (meaning having the assignee be limited to Jira software users or a specific user role, and the reporter be limited to portal only customers, etc) I believe that would benefit more users. 

            Jenn McGugan added a comment - - edited While I'd like to limit the assignee user picker to only those who work the back end of the tickets, both the reporter field and the requested participants fields for our system need to see and be able to choose from the portal only customers. If you can make it so we can choose which fields are limited by specific criteria, which would be unique for each field, (meaning having the assignee be limited to Jira software users or a specific user role, and the reporter be limited to portal only customers, etc) I believe that would benefit more users. 

            Chris Card added a comment -

            I'd like to add my support for this issue as well. JSM Customers should not appear in the assignee/reporter lists of internal Jira projects. 

            Chris Card added a comment - I'd like to add my support for this issue as well. JSM Customers should not appear in the assignee/reporter lists of internal Jira projects. 

            Evaldas added a comment -

            I agree with restrictions to such fields as Reporter, HOWEVER I don't agree with such restrictions to all custom fields... For example, we need custom fields of (single/multiple) user-pick for informational purposes and we want to be able to select a user from the full list...

            Evaldas added a comment - I agree with restrictions to such fields as Reporter, HOWEVER I don't agree with such restrictions to all custom fields... For example, we need custom fields of (single/multiple) user-pick for informational purposes and we want to be able to select a user from the full list...

            This is a big bug. Please fix. Users that do not have a Jira software or JSM license can be accidentally selected on a user picker field.

            Venkat Nagarajan added a comment - This is a big bug. Please fix. Users that do not have a Jira software or JSM license can be accidentally selected on a user picker field.

            This would be a great initiative. 

            We have a field that is type "user picker / multiple users". It allows you to select Portal Only Customers. This should not be allowed as they are not users of Jira.

            Hence, I vote for this change

            Rowan Brown added a comment - This would be a great initiative.  We have a field that is type "user picker / multiple users". It allows you to select Portal Only Customers. This should not be allowed as they are not users of Jira. Hence, I vote for this change

            We have more than 5000 Jira Software Users and more than 3000 Confluence Users in our Cloud and since one year, we're also running Jira Service Management. And the complaints from Software developers get more and more why they can find so many private email addresses or accounts that are not belonging to our company. We really hope that there will be a solution in the near future. Thank you very much!

            Gabriel Ender added a comment - We have more than 5000 Jira Software Users and more than 3000 Confluence Users in our Cloud and since one year, we're also running Jira Service Management. And the complaints from Software developers get more and more why they can find so many private email addresses or accounts that are not belonging to our company. We really hope that there will be a solution in the near future. Thank you very much!

            This is crucial for security purposes. Please provide us with a resolution.

            Angelica Freire de Carvalho Reis added a comment - This is crucial for security purposes. Please provide us with a resolution.

            This ia a very BIG BUG!!! please fix this asap!!!

            Dennis Verdaasdonk added a comment - This ia a very BIG BUG!!! please fix this asap!!!

              Unassigned Unassigned
              d7c646f367ae Valentijn Scholten
              Votes:
              225 Vote for this issue
              Watchers:
              200 Start watching this issue

                Created:
                Updated: