Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1587

Service Desk users should be able to change email notification type

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.3
    • None
    • None
    • 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.

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

      Service Desk users may have a need to change email notification type (text or html). Based on actual use cases and votes, we will speed up the process to build it.

          Form Name

            [JSDSERVER-1587] Service Desk users should be able to change email notification type

            Luca Sokoll added a comment -

            +1 for this please

            Luca Sokoll added a comment - +1 for this please

            Hakan OTAL added a comment -

            Dear all ,
            Thanks for update.
            i am waiting related feature asap.
            Regards.

            Hakan OTAL added a comment - Dear all , Thanks for update. i am waiting related feature asap. Regards.

            Philip Colmer added a comment -

            Hi

            Thanks for the update.

            Regards

            Philip

            Philip Colmer added a comment - Hi Thanks for the update. Regards Philip

            Joseph Huynh (Inactive) added a comment -

            Hi Philip,

            Thanks for raising this. This is in fact a limitation for customers(free users without any jira license).
            In another word, the current user email type preference is only accessible for engineers (JIRA users).
            To change Email Type your customers need to go to Profile and edit personal Preference.

            In the upcoming release, Service desk will be smart enough to detect your customer's email client preferences.
            i.e. If you set the global settings for email type to HTML.
            customer A set his settings on Gmail client to receive only text, will receive text version of the notification.
            customer B set his settings on Hotmail client to html, will receive html version.

            I hope that helps.

            Joseph Huynh (Inactive) added a comment - Hi Philip, Thanks for raising this. This is in fact a limitation for customers(free users without any jira license). In another word, the current user email type preference is only accessible for engineers (JIRA users). To change Email Type your customers need to go to Profile and edit personal Preference. In the upcoming release, Service desk will be smart enough to detect your customer's email client preferences. i.e. If you set the global settings for email type to HTML. customer A set his settings on Gmail client to receive only text, will receive text version of the notification. customer B set his settings on Hotmail client to html, will receive html version. I hope that helps.

            Philip Colmer added a comment -

            Definitely needs to be a user preference. Personally, I like the richness of HTML email but a lot of our engineers/customers work with text-driven email tools and therefore insist on plain text. Applying a single global setting is going to upset somebody.

            Philip Colmer added a comment - Definitely needs to be a user preference. Personally, I like the richness of HTML email but a lot of our engineers/customers work with text-driven email tools and therefore insist on plain text. Applying a single global setting is going to upset somebody.

              Unassigned Unassigned
              pdoan Phuong Doan (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: