Open issues

Order by Priority
  1. Suggestion
    JSDSERVER-3204Option to remove the tag "Optional" from non required fields on Customer Portal.
  2. Suggestion
    JSDSERVER-6034Ability to define landing page after creating an issue on the Portal
  3. Suggestion
    JSDSERVER-12371Ability to increase attachment size for Assets
  4. Suggestion
    JSDSERVER-14833Assets CSV export to include inbound / outbound references
  5. Suggestion
    JSDSERVER-15184Manage versions should have separate permission levels
  6. Suggestion
    JSDSERVER-15679Introduce null-safety to Assets import result assembler
  7. Suggestion
    JSDSERVER-16290Terraform / atlassian-operations_user - Allow lookup by account ID
  8. Suggestion
    JSDSERVER-15186Add a web-based user interface to Assets Discovery
  9. Suggestion
    JSDSERVER-1942Allow HTML/Rich text formatting in tickets created through email in Service Desk
  10. Suggestion
    JSDSERVER-4056Expire Satisfaction Feedback Token
  11. Suggestion
    JSDSERVER-4749Export Satisfaction Report
  12. Suggestion
    JSDSERVER-5950Expose Customer Satisfaction survey API
  13. Suggestion
    JSDSERVER-15403It would be helpful to add an AQL Function to be able to check for Inactive/Active User Status for User attribute type searches.
  14. Suggestion
    JSDSERVER-16124Allow Request Types to be hidden on the UI and only accessible via direct link
  15. Suggestion
    JSDSERVER-8461Add ability to trigger "Filter Assign Scope" retroactively for existing issues
  16. Suggestion
    JSDSERVER-15278Add an option that allows disabling the automatic addition of mentioned users as request participants
  17. Suggestion
    JSDSERVER-8471Make the Satisfaction Comment field available in Issue Navigator
  18. Suggestion
    JSDSERVER-16286Use API Token Name for updates by API
  19. Suggestion
    JSDSERVER-11165Support Insight Discovery Agent on Non-Windows platform
  20. Suggestion
    JSDSERVER-16288Allow customization of default emoji reactions on Jira comment threads
  21. Suggestion
    JSDSERVER-16236Portal-Only Customer-facing Forum / Community
  22. Suggestion
    JSDSERVER-15659Agents can not use Login Free Portal, they get an error when creating a new request
  23. Suggestion
    JSDSERVER-16284Allow Assets custom fields to be searched from quick search
  24. Suggestion
    JSDSERVER-16285Prevent automatic unsubscribe due to email security scanner link clicks
  25. Suggestion
    JSDSERVER-8511Ability to have permissions for JSM queue management separate from the Administrator role
  26. Suggestion
    JSDSERVER-15680Show Assets with Attributes on Customer Portal
  27. Suggestion
    JSDSERVER-16283Provide a field on the portal to show customers their position in the queue
  28. Suggestion
    JSDSERVER-16287Requests view should be able to arrange tickets by date
  29. Suggestion
    JSDSERVER-7767Provide an option to raise the number of results shown in the search when filling referenced objects or implement an object picker
  30. Suggestion
    JSDSERVER-13973Improving UX on Asset object dropdown list
  31. Suggestion
    JSDSERVER-15112Introduce search performance improvements for "Request Participants" field
  32. Suggestion
    JSDSERVER-93Allow editing of fields / details through the service project request (post-creation)
  33. Suggestion
    JSDSERVER-3746Create linked issue in another Jira instance and automated notifications
  34. Suggestion
    JSDSERVER-15356Provide a way to Merge Duplicate Assets Objects
  35. Suggestion
    JSDSERVER-15591JSM Customer Portal loads slower for customer accounts compared to agent accounts
  36. Suggestion
    JSDSERVER-15288Assets REST API to perform bulk add watchers to multiple objects or entire object type
  37. Suggestion
    JSDSERVER-16280Assets Discovery agent scan files name should include hostname
  38. Suggestion
    JSDSERVER-16281Amend Assets Discovery agent document tag for password
  39. Suggestion
    JSDSERVER-4417Add email domain to Customer Organisation
  40. Suggestion
    JSDSERVER-7425Placeholder for Service Desk request types
  41. Suggestion
    JSDSERVER-7451Add an IQL function to search in a recursive way outbound references
  42. Suggestion
    JSDSERVER-16073Integrate System Status into the Customer Portal
  43. Suggestion
    JSDSERVER-2044As a Service Desk User, I would like notifications to contain the request history
  44. Suggestion
    JSDSERVER-3118Allow users to configure keyboard shortcut {{CTRL+Enter}}
  45. Suggestion
    JSDSERVER-4269Do not display non-functional errors of mail parsing in description
  46. Suggestion
    JSDSERVER-5137Knowledge Base articles do not scale properly on JSD mobile view in supported browsers
  47. Suggestion
    JSDSERVER-15618Increase the "load more limit" for the Assets - Confluence Macro.
  48. Suggestion
    JSDSERVER-16270Feature to export a report of archived objects.
  49. Suggestion
    JSDSERVER-16273Add mixed content support for the JSM Mail Channel when the setting "HTML email parsing" is turned OFF
  50. Suggestion
    JSDSERVER-433Auto-refresh and/or warn user if the ticket has changed
Refresh results
270 of 3913
Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-16288

Allow customization of default emoji reactions on Jira comment threads

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Issue View
    • We collect Jira Service Desk 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.

      Currently, Jira provides a fixed set of emoji reactions (👍 👏 🔥 ❤️ 😮 😕) on comment threads. These emojis are helpful for quick feedback, but teams often have their own communication styles or meanings for reactions.

      We request the ability to:

      Customize the default set of emoji reactions shown when hovering over comments.
      Configure default reactions per project or workspace.
      Optionally disable certain emojis or reorder them based on usage.

      This feature would improve clarity, align Jira with team culture, and provide more meaningful micro-feedback in workflows.

            There are no comments yet on this issue.

              Unassigned Unassigned
              e22f70240d0c Dana S
              Votes:
              5 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: