We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-6140

As a Service Desk Admin I would like to be able to restrict Customers from adding Agents to Requests as Participants

    • 1
    • 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.

      Problem Definition

      When a Customer adds an Agent to their request as a participant, that agent is subsequently treated as a Customer for the purposes of triggering SLAs with events like "Comment: for customer"

      Suggested Solution

      Implement a way to restrict Customer's abilities to add Agents as Request Participants, or, treat Customer-added Agents differently in some other way to avoid this problem.

      Workaround

      Ask Agents to manually remove themselves from being a Request Participant before acting further in order to have their events be fired/processed as intended.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Service Management Cloud'
            1. Jira Service Management Cloud
            2. JSDCLOUD-6140

            As a Service Desk Admin I would like to be able to restrict Customers from adding Agents to Requests as Participants

              • 1
              • 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.

                Problem Definition

                When a Customer adds an Agent to their request as a participant, that agent is subsequently treated as a Customer for the purposes of triggering SLAs with events like "Comment: for customer"

                Suggested Solution

                Implement a way to restrict Customer's abilities to add Agents as Request Participants, or, treat Customer-added Agents differently in some other way to avoid this problem.

                Workaround

                Ask Agents to manually remove themselves from being a Request Participant before acting further in order to have their events be fired/processed as intended.

                        Unassigned Unassigned
                        dmark@atlassian.com Danny (Inactive)
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            dmark@atlassian.com Danny (Inactive)
                            Votes:
                            1 Vote for this issue
                            Watchers:
                            1 Start watching this issue

                              Created:
                              Updated:
                              Resolved: