Open issues

Order by Priority
  1. Suggestion
    JSDCLOUD-1268Support adding a Jira group to the "Request participants" field
  2. Suggestion
    JSDCLOUD-1829Bulk Import Customers or Organizations from External File
  3. Suggestion
    JSDCLOUD-1928Allow admin to configure default tab for Comment field
  4. Suggestion
    JSDCLOUD-2044Include request history in customer notifications
  5. Suggestion
    JSDCLOUD-2297Ability to have condition to start, pause and stop SLA based on custom field value
  6. Suggestion
    JSDCLOUD-4552Customize the columns displayed on the portal requests list for customers
  7. Suggestion
    JSDCLOUD-5008Remove the line from all the notifications email
  8. Suggestion
    JSDCLOUD-5980Allow customer to view their issue detail without login to Customer Portal
  9. Suggestion
    JSDCLOUD-6677Allow to customize transition screen for Customer Portal
  10. Suggestion
    JSDCLOUD-9635Ability to add a request participant only by email without creating a customer first
  11. Suggestion
    JSDCLOUD-9872Ability to link more than 20 objects to a single Jira issue
  12. Suggestion
    JSDCLOUD-9979Last Activity date not updated for users with only site access (JSM customers)
  13. Suggestion
    JSDCLOUD-11054Ability to customize Approval Notifications
  14. Suggestion
    JSDCLOUD-12371Provide automation conditions to allow removal of Request Participants
  15. Suggestion
    JSDCLOUD-13551Ability to trigger an automation based on Forms attached
  16. Suggestion
    JSDCLOUD-13559Ability to use other Asset Object Schema in Affected Services Field
  17. Suggestion
    JSDCLOUD-13861Allow syncing customer details through SCIM/Okta or any third party identity provider
  18. Suggestion
    JSDCLOUD-14212Trying to change group name fails due to CMDB - Assets usage
  19. Suggestion
    JSDCLOUD-16240Add ability to manage/enforce JSM Customer Access settings at Org level
  20. Suggestion
    JSDCLOUD-4687As an admin, I'd like to be able to hide the breadcrumb link on each request page
  21. Suggestion
    JSDCLOUD-5981Disable portal automatic responses based on customer notifications settings
  22. Suggestion
    JSDCLOUD-7548Include Domain Level Restrictions For Email Request
  23. Suggestion
    JSDCLOUD-10088Assets Automation: Object smart value for "User" doesn't return User email address.
  24. Suggestion
    JSDCLOUD-10317Ability to hide Assets object custom field in customer portal
  25. Suggestion
    JSDCLOUD-10461Assets: Enhanced capability of Services object schema like regular schemas
  26. Suggestion
    JSDCLOUD-11075Add API to be able to retrieve Assets object field values
  27. Suggestion
    JSDCLOUD-11131Add incoming mail monitoring & provide a warning or alert if an email has failed to send
  28. Suggestion
    JSDCLOUD-11392Assets Automation: Add the ability to add/update/set object attributes like a multi-select in Assets field via Automation
  29. Suggestion
    JSDCLOUD-11399Forms automation: Attach/copy forms for multiple projects
  30. Suggestion
    JSDCLOUD-11515When an object has a User Attribute and is linked to a user, the object will be displayed in their User Profile
  31. Suggestion
    JSDCLOUD-12358Automation - Improve Edit Issue Action to include other fields, e.g. Organisation, Resolution field or custom fields
  32. Suggestion
    JSDCLOUD-12754Make the "Block transition until approval" condition work for any transition in the workflow in JSM Cloud
  33. Suggestion
    JSDCLOUD-12765Canned Responses - Resolution/Transition Screen
  34. Suggestion
    JSDCLOUD-12923Allow administrators to configure whether approvers lose access to previously approved issues when they are removed from the approver field
  35. Suggestion
    JSDCLOUD-13528Provide Log of customer notifications that are successfully sent
  36. Suggestion
    JSDCLOUD-13751Automatically update present object types and attributes while import
  37. Suggestion
    JSDCLOUD-15350Provide URL functionality for pre-populated asset custom field
  38. Suggestion
    JSDCLOUD-119Allow to rename an existing SLA
  39. Suggestion
    JSDCLOUD-1034Queue containing issues from multiple service desks
  40. Suggestion
    JSDCLOUD-1422Sub-tasks as an applicable issue type for Request Types
  41. Suggestion
    JSDCLOUD-1703Make "Request participants" custom field available to security level configuration
  42. Suggestion
    JSDCLOUD-1914As a user, I would like to add Customer Request Type, Affected Services field into Dashboard Gadget
  43. Suggestion
    JSDCLOUD-4636View linked issue in the Customer Portal
  44. Suggestion
    JSDCLOUD-5746Change the customer e-mail address
  45. Suggestion
    JSDCLOUD-5861Allow widget without login-free portal
  46. Suggestion
    JSDCLOUD-5975Have option to change "Reply-to" email to another verified domain
  47. Suggestion
    JSDCLOUD-6191Vacation of agents
  48. Suggestion
    JSDCLOUD-8422SLA should be automatically calculated after JSON import if they contain issue history
  49. Suggestion
    JSDCLOUD-8509Shareable links should be formatted or customizable to prompt users to log in
  50. Suggestion
    JSDCLOUD-8749Ability to have issue level security in Team-managed (former next-gen) projects
Refresh results
204 of 4445
Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-2044

Include request history in customer notifications

    • 267
    • 30

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

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

      Product Update - Dec 20, 2024

      HI Everyone,

      An update on this issue.

      We've been working on the roadmap for teh first half of next year and have finalised the first quarter.

      Whilst this issue has a high number of votes, there are several other issues with greater impact and votes that we will be pushing ahead with.

      This issue still in consideration for the next phase of work after that and I will update this ticket if the status is updated. Thanks for your patience!

      Regards,

      Ben Costello
      Principal Product Manager, JSM Emails/

      Currently, Service Desk notifications will only contain the data relevant to the event that has triggered the notification.
      In order to have a complete overview on mail, having historic data available in the mail notifications would be very convenient to have.
      In particular when forwarding this email to another person to inform them of the reqest, and the history within.

              1bbfd485bf63 Ben Costello
              mnassette MJ (Inactive)
              Votes:
              687 Vote for this issue
              Watchers:
              382 Start watching this issue

                Created:
                Updated: