Log inSkip to main contentSkip to sidebar
Something went wrong, please try again.
Create and track feature requests for Atlassian products.
  • More
    DashboardsProjectsIssues
  • Give feedback to Atlassian
  • Help
    • Jira Core help
    • Keyboard Shortcuts
    • About Jira
    • Jira Credits
  • Log In
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.

Open issues

  • All issues
  • Open issues
  • Done issues
  • Viewed recently
  • Created recently
  • Resolved recently
  • Updated recently
View all issues and filters
Order by Priority
  1. Suggestion
    JSWSERVER-26466Improve basic knowledge of virtual service Agent response on JSM helpcenter portal
  2. Suggestion
    JSWSERVER-26463Epic Link picker in basic search brings Done issues by default
  3. Suggestion
    JSWSERVER-9455Ability to create a hierarchy of Epics instead of a single level
  4. Suggestion
    JSWSERVER-21080Allow Cluster Monitoring page to show the nodes load on Windows environments
  5. Suggestion
    JSWSERVER-24817Being able to add a hierarchy level between Epic and Story
  6. Suggestion
    JSWSERVER-24818Allow Hierarchy flexibility between levels
  7. Suggestion
    JSWSERVER-9707Sprint Health Gadget for completed Sprints
  8. Suggestion
    JSWSERVER-5720New "Base Swimlanes On" option for "versions"
  9. Suggestion
    JSWSERVER-11216Allow sprints to be archived
  10. Suggestion
    JSWSERVER-11952Ability to configure a default board to show for a project
  11. Suggestion
    JSWSERVER-24771Increase the project, issue, and team limits in Plan
  12. Suggestion
    JSWSERVER-24995Filter by parent in Portfolio
  13. Suggestion
    JSWSERVER-26461Kerberos support for outbound traffic
  14. Suggestion
    JSWSERVER-26460Show "Upgrade from" data in "Latest Upgrade Report"
  15. Suggestion
    JSWSERVER-26462Dependencies report Rollup doesn't work when "Team" is filtered in the Roadmap
  16. Suggestion
    JSWSERVER-5212As a Rapid Board User planning a project, I want the subtask estimates (both time and story points) to count towards my sprint marker estimates.
  17. Suggestion
    JSWSERVER-6135Ability to export the Sprint reports into a common format
  18. Suggestion
    JSWSERVER-9167Provide ability to automatically sum estimates from sub-tasks in user stories
  19. Suggestion
    JSWSERVER-15276Simplified Workflow: add option to disable the creation of new statuses
  20. Suggestion
    JSWSERVER-15655Ability to add columns to Epic Issue list on Epic
  21. Suggestion
    JSWSERVER-19959Add granular permissions relating to version control
  22. Suggestion
    JSWSERVER-20097JQL search for issues added and removed from a sprint
  23. Suggestion
    JSWSERVER-21238Support Github Cloud Enterprise organisation managed by Azure IdP
  24. Suggestion
    JSWSERVER-21245Ability to add custom columns in release page (view)
  25. Suggestion
    JSWSERVER-25077Add Original Story Points field to Portfolio new experience
  26. Suggestion
    JSWSERVER-25190Allow Advanced Roadmaps to Group by any custom field
  27. Suggestion
    JSWSERVER-19825Add (optionally) field names on card layout
  28. Suggestion
    JSWSERVER-26175System field "Due Date" has had its name label changed from "Due Date" to "Due Date (d/MMM/yy)"
  29. Suggestion
    JSWSERVER-7265As a user, I want to make estimates visible on cards in Kanban board
  30. Suggestion
    JSWSERVER-8851Ability to view and prioritise epics in the backlog
  31. Suggestion
    JSWSERVER-12228As a Scrum Master, I would like to have changes in Sprint dates shown on Reports
  32. Suggestion
    JSWSERVER-20277Update Documentation - Clarify that when completing a sprint, sending incomplete issues to the next sprint will still send issues to the backlog if they are not visible from the current board.
  33. Suggestion
    JSWSERVER-20433Sprint Goal should support multi line text input
  34. Suggestion
    JSWSERVER-20772Product Goal for Product Backlog
  35. Suggestion
    JSWSERVER-24916Display lines between issue dependencies similar to the Advanced Roadmaps Cloud version
  36. Suggestion
    JSWSERVER-25115Milestones
  37. Suggestion
    JSWSERVER-25122Advanced Roadmaps - Add support for more custom fields to the plan view
  38. Suggestion
    JSWSERVER-25146Change Issue status from within Jira Advanced Roadmap
  39. Suggestion
    JSWSERVER-7992Ability to see sub-tasks in the backlog
  40. Suggestion
    JSWSERVER-10762Create a dashboard gadget for the Velocity Chart
  41. Suggestion
    JSWSERVER-13011Ability to get the details of the administrator of the board through JIRA Agile (Software) REST API
  42. Suggestion
    JSWSERVER-14931Disable or limit the "Create Branch" option
  43. Suggestion
    JSWSERVER-15868Update api/2/reindex section from Rest API reference
  44. Suggestion
    JSWSERVER-21503Usage statistics for marketplace apps
  45. Suggestion
    JSWSERVER-21596As a jira admin, I want to capture if DVCS WebHooks exists for any given repository/account
  46. Suggestion
    JSWSERVER-26009Request to modify the default image size in Jira description/comments
  47. Suggestion
    JSWSERVER-20108add "create sub-task" to story right-click menu on board
  48. Suggestion
    JSWSERVER-20950Add a single issue to MS Teams integration.
  49. Suggestion
    JSWSERVER-19854Error when changing time zone
  50. Suggestion
    JSWSERVER-14633Provide a separate permission for users to assign issue to Active and Future Sprint
Refresh results
1 2 3 4 5Next >>
1 of 2995
Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-26466

Improve basic knowledge of virtual service Agent response on JSM helpcenter portal

Log In
Gathering Interest
Export
undefinedView workflow
XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • (Advanced Roadmaps) Other
    • None
    • We collect Jira 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.

      Why can't Atlassian AI for Jira Service Management (CLOUD) reason beyond the content it has access to for basic troubleshooting?

      It is a shame that the AI only act based on Intents and given knowledge base. This means for every possible issue you need to write an intent or add to knowledge base.

      This is a hell of a lot of work on updating knowledge. It does not make the AI that efficient if you must have someone that updates the knowledge base everyday. Just like Copilot chat bot I created for IT support, I can give it a knowledge base, but it also picks up basic IT troubleshooting. Example, if it is ask that someone's monitor is not working, then a basic troubleshooting is searched online, because it is not in our knowledge base, but it is basis troubleshooting. 

          Form Name

            • All
            • Comments
            • Work Log
            • History
            • Activity
            Marv dlf created issue - 6 hours ago

              Unassigned Unassigned
              d79176d67ee4 Marv dlf
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                5 hours ago
                Updated:
                5 hours ago

                  • Atlassian Jira Project Management Software
                  • About Jira
                  • Report a problem
                  • Privacy policy
                  • Notice at Collection

                  Atlassian