All issues

Order by Created
  1. Suggestion
    JSDCLOUD-17411Ability to give option for user to "Escalate" in virtual agent after provided article suggestion
  2. Suggestion
    JSDCLOUD-17410Ability to set a field from an intent even if it is not part of the Request Form
  3. Suggestion
    JSDCLOUD-17409Ability to import public holiday information in JSM Operations
  4. Suggestion
    JSDCLOUD-17408Add Who is on call information to All on-call schedules panel > Responder
  5. Suggestion
    JSDCLOUD-17407Global Option to Hide Operations under JSM sidebar for all users
  6. Suggestion
    JSDCLOUD-17406Expose JSM Project-Level Feature Flags via REST API (Parity with Jira Software)
  7. Bug
    JSDCLOUD-17405Using Cascading Options with Jira forms and Assets
  8. Bug
    JSDCLOUD-17404Help Center: Inaccurate textual description specified for interactive image
  9. Bug
    JSDCLOUD-17403Inaccurate search results while linking Confluence space in a JSM project
  10. Bug
    JSDCLOUD-17402Saving/Enabling a widget results in error "We can't save the Widget right now. Try again in a little while."
  11. Bug
    JSDCLOUD-17401Help Center: Focus moves inappropriately
  12. Bug
    JSDCLOUD-17400Help Center: Main landmark incorrectly wraps the entire page content
  13. Suggestion
    JSDCLOUD-17399Several rich-text editor features available in the JSM agent view are missing from the customer portal.
  14. Bug
    JSDCLOUD-17398JSM Chat: User who's name multibyte characters are not displayed as suggestions on Slack
  15. Suggestion
    JSDCLOUD-17396Description of fields in Atlassian Assist
  16. Bug
    JSDCLOUD-17393Attachments getting Orphaned and cannot be Deleted
  17. Bug
    JSDCLOUD-17397The VCard link in the Compass migration wizard leads to 404 (Page not found) Error.
  18. Bug
    JSDCLOUD-17392Unable to Change Limit for Assets
  19. Suggestion
    JSDCLOUD-17395Apply approval changes in workflows to existing issues retroactively
  20. Bug
    JSDCLOUD-17391Graphical glitch in Heat map dashboard visual in data manager
  21. Bug
    JSDCLOUD-17388Setting email back to "Unread" in custom email request for failed email doesn't get processed as new ticket or added as a comment
  22. Suggestion
    JSDCLOUD-17387AI answers for Virtual agent should have ability for single KB article to have multiple language versions linked together under one entry.
  23. Suggestion
    JSDCLOUD-17386Enable searching with keywords in other languages in the user picker field within Atlassian Assist (Slack).
  24. Suggestion
    JSDCLOUD-17385Enable Work Type Hierarchy for JSM Premium
  25. Suggestion
    JSDCLOUD-17383Improve select list cascading fields in JSM Chat Assist
  26. Suggestion
    JSDCLOUD-17382Improve Error Logging for Delayed Target Server Responses
  27. Bug
    JSDCLOUD-17381Asset object keys are ordered alphabetically instead of numerically when sorting by key
  28. Suggestion
    JSDCLOUD-17380Add the ability to use Attribute id in AQL instead of name
  29. Suggestion
    JSDCLOUD-17379VSA: Allow AI answer in MS Teams/ Slack without adding their IP range in IP allowlist when enabled
  30. Bug
    JSDCLOUD-17378Special characters on KB articles are not rendered in JSM Reports
  31. Suggestion
    JSDCLOUD-17377Add support to configure Assets fields with schemas from other sites within the same organization.
  32. Suggestion
    JSDCLOUD-17376Change Service agent connected to project
  33. Suggestion
    JSDCLOUD-17375Add advanced filtering options to the Help Center requests page
  34. Bug
    JSDCLOUD-17374When creating a new Journey user with the Administer Jira Global permission can't Add Automation rules to Journeys
  35. Suggestion
    JSDCLOUD-17373Display the error on the UI.
  36. Suggestion
    JSDCLOUD-17372provide ability to show real time SLA updates on the issue view
  37. Bug
    JSDCLOUD-17371Raise request button in Assist app home in Slack for JSM Chat shows all visible request channel connected, irrespective of the channel.
  38. Suggestion
    JSDCLOUD-17370JSM Knowledge base error due to deactivated Confluence Site
  39. Suggestion
    JSDCLOUD-17369Implement numerical sorting for IP address attributes
  40. Bug
    JSDCLOUD-17368Japanese IME is not working properly in Assets "Text area" attributes
  41. Suggestion
    JSDCLOUD-17366Request type restriction not updated when the work item request type is updated
  42. Bug
    JSDCLOUD-17394When Summary field is updated, new value is not shown unless page is refreshed
  43. Bug
    JSDCLOUD-17365Filter issue scope" AQL no longer updates dynamically when Issue Type is changed on transition screen
  44. Suggestion
    JSDCLOUD-17364Atlassian Assist with Coffee Feature
  45. Bug
    JSDCLOUD-17363Request type value not copied while moving work item
  46. Bug
    JSDCLOUD-17362Automation rules begin to fail after Assets new Arch
  47. Suggestion
    JSDCLOUD-17361Retention and accessibility of email processing logs after mailbox dissociation
  48. Suggestion
    JSDCLOUD-17360System-level detection and warning for duplicate mailbox associations across all JSM projects/sites
  49. Bug
    JSDCLOUD-17359Assets Imports: When using an Select type Attribute as the identifier in the Assets import it creates duplicate objects
  50. Suggestion
    JSDCLOUD-17358Copying data from JSM PROD to Sandbox, doesnot copy details of customer and organisation
Refresh results
1 of 12829
Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-17411

Ability to give option for user to "Escalate" in virtual agent after provided article suggestion

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

      Current State:

      Currently , escalation flow only can be set within intent configuration. However , there are scenario where if customer query is responded by AI Answers , customer still need help , hence they prefer to escalate to create a ticket , which currently it is not available

      Proposed Future State:

      Provide option for customer to create ticket/escalate after getting answers from AI . This option should be provided outside the intent configuration.

       

      Alternative (e.g. Third Party Plugin):

      No workaround

            Atiqah Roslan created issue -

              Unassigned Unassigned
              nroslan Atiqah Roslan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: