Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-1700

When Raise Request on behalf of customer from JIRA and change request type a notification should be sent

XMLWordPrintable

    • 0
    • 19

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

      Atlassian Update - October 2023

      Hi Everyone,

      Thank you for previously raising this feature request and bringing it to our attention.

      Within our company roadmap and work capacity, we try to address or review each feature request but admit that not each one will be implemented. To continue the culture of being honest and open, we are closing this ticket to focus on our upcoming roadmap for all Jira Service Management Cloud users. You can visit Atlassian Cloud Roadmap to learn more about what was recently released and the upcoming roadmap.

      Thank you again for providing valuable feedback to our team!

      Arjun Ganapathy
      Jira Service Management Cloud team

      NOTE: This suggestion is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      For the times I need to create a ticket in JIRA and change the Reporter role, it would be nice for the customer to get an email notification when I have edited the Request Type and made it viewable from within the portal.

      Currently I can add an external comment to the ticket, and the customer will receive this message, but it would be good to be automated.

      Flow

      • Create ticket in JIRA (for a SD project) and change reporter to customer
      • Set the customer request type for the ticket

      Expected outcome

      • Customer receives an email stating that request is available to view

      Workaround

      As an agent, use the Raise this request on behalf of feature within the Customer Portal.
      Notifications will be sent correctly on issue create, in this scenario.

        1. image-2017-03-14-22-54-25-307.png
          image-2017-03-14-22-54-25-307.png
          49 kB
        2. Screenshot_238.png
          Screenshot_238.png
          20 kB

              Unassigned Unassigned
              mmcmahon Matthew McMahon (Inactive)
              Votes:
              20 Vote for this issue
              Watchers:
              22 Start watching this issue

                Created:
                Updated:
                Resolved: