• Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 1
    • We collect Jira Service Desk 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.

      Issue Summary

      If a user sends an email that contains CC field and a user who is not meant to be a customer in the project is added to the project, there is no way to simply delete the user in the Customer page of the project.

      Usage Scenario

      If a user sends an email and the company's security policy changes and they need to remove users who were added to the CC field of emails processed and made into users, they agents do not have any way to remove such users directly from the Customer page of the service desk project.

      Expected Behavior

      An would appear at the end of the column for the customer that allows the agent to directly delete the user they do not need similar to what is available for organizations.

      Actual Behavior

      There are no direct ways to delete the user from the project as a customer.

      Workaround
      1. Hover your mouse over the user.
      2. When the pop-up comes up, Select More and from the options presented to you, select Administer User.
      3. Press Action and Select Delete User

      If the user is a JIRA user or you need them as a customer in other projects, instead of step Deleting the user, use the following steps to remove them:

      • Press View Project Roles.
        • This would list all projects the user has a role in
      • Press the Edit Project Roles.
      • Uncheck the user from the Service Desk customer role.
      • Save your changes.

            [JSDSERVER-5374] Delete Customer

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: