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

Allow Jira Service Desk portal notification to use an Email Settings from Jira General Configurationn

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None
    • None
    • 1
    • 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.

      Atlassian Update – 24 March 2021

      Hi everyone,

      Thank you for your interest in this issue.

      After investigating this request further, we believe it has been incorrectly categorised as a feature suggestion rather than a bug. Jira Service Management notifications are currently not respecting the global Jira setting for ‘email from’.

      We understand that this issue can cause confusion for your customers and it is an issue we would like to resolve. Thank you for your votes and comments on this ticket, it has surfaced it for our attention.

      The related public bug ticket (JSDSERVER-3597) will be reopened and triaged accordingly - please follow progress on that ticket.

      Kind regards,

      Charlie

      Jira Service Management, Server & Data Center

      Problem Definition

      Currently, Jira service desk portal notification is using a different notification header that uses in Jira notification.

      Jira Service Desk Portal notification

      Jira notification

       

      Jira notification email is using an Email from settings from Jira General configuration:

      Suggested Solution

      It will be better if service desk notification will follow the same template settings while sending email notification.

        1. jira notification email.png
          22 kB
          Amirul Ikhwan Omar
        2. screenshot-1.png
          59 kB
          Amirul Ikhwan Omar
        3. service desk notification email.jpg
          44 kB
          Amirul Ikhwan Omar

            [JSDSERVER-5911] Allow Jira Service Desk portal notification to use an Email Settings from Jira General Configurationn

            Charlie Marriott made changes -
            Resolution New: Tracked Elsewhere [ 15 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Link New: This issue is superseded by JSDSERVER-3597 [ JSDSERVER-3597 ]

            Atlassian Update – 24 March 2021

            Hi everyone,

            Thank you for your interest in this issue.

            After investigating this request further, we believe it has been incorrectly categorised as a feature suggestion rather than a bug. Jira Service Management notifications are currently not respecting the global Jira setting for ‘email from’.

            We understand that this issue can cause confusion for your customers and it is an issue we would like to resolve. Thank you for your votes and comments on this ticket, it has surfaced it for our attention.

            The related public bug ticket (JSDSERVER-3597) will be reopened and triaged accordingly - please follow progress on that ticket.

            Kind regards,

            Charlie

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 24 March 2021 Hi everyone, Thank you for your interest in this issue. After investigating this request further, we believe it has been incorrectly categorised as a feature suggestion rather than a bug. Jira Service Management notifications are currently not respecting the global Jira setting for ‘email from’ . We understand that this issue can cause confusion for your customers and it is an issue we would like to resolve. Thank you for your votes and comments on this ticket, it has surfaced it for our attention. The related public bug ticket ( JSDSERVER-3597 ) will be reopened and triaged accordingly - please follow progress on that ticket. Kind regards, Charlie Jira Service Management, Server & Data Center
            Charlie Marriott made changes -
            Description Original: h3. Problem Definition

            Currently, Jira service desk portal notification is using a different notification header that uses in Jira notification.
            h4. *Jira Service Desk Portal notification*

            !service desk notification email.jpg|thumbnail!
            h4. *Jira notification*
            !jira notification email.png|thumbnail! 

            Jira notification email is using an *Email from* settings from Jira General configuration:
             !screenshot-1.png|thumbnail!
            h3. Suggested Solution

            It will be better if service desk notification will follow the same template settings while sending email notification.
            New: {panel:title=Atlassian Update – 24 March 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}

            Hi everyone,

            Thank you for your interest in this issue.

            After investigating this request further, we believe it has been incorrectly categorised as a feature suggestion rather than a bug. Jira Service Management notifications are currently not respecting the [global Jira setting for ‘email from’|https://confluence.atlassian.com/adminjiraserver/configuring-jira-application-options-938847824.html#ConfiguringJiraapplicationoptions-settingsGeneralsettings].

            We understand that this issue can cause confusion for your customers and it is an issue we would like to resolve. Thank you for your votes and comments on this ticket, it has surfaced it for our attention.

            The related public bug ticket ([JSDSERVER-3597|https://jira.atlassian.com/browse/JSDSERVER-3597]) will be reopened and triaged accordingly - please follow progress on that ticket.

            Kind regards,

            Charlie

            Jira Service Management, Server & Data Center{panel}

            h3. Problem Definition

            Currently, Jira service desk portal notification is using a different notification header that uses in Jira notification.
            h4. *Jira Service Desk Portal notification*

            !service desk notification email.jpg|thumbnail!
            h4. *Jira notification*
            !jira notification email.png|thumbnail! 

            Jira notification email is using an *Email from* settings from Jira General configuration:
             !screenshot-1.png|thumbnail!
            h3. Suggested Solution

            It will be better if service desk notification will follow the same template settings while sending email notification.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012255 ] New: JAC Suggestion Workflow 3 [ 3647233 ]
            Andy Nguyen (Inactive) made changes -
            Link New: This issue duplicates JSDSERVER-702 [ JSDSERVER-702 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2743482 ] New: JAC Suggestion Workflow [ 3012255 ]
            Amirul Ikhwan Omar (Inactive) made changes -
            Summary Original: Allow Jira Service Desk portal notification to use an Email from Settings from Jira General Configurationn New: Allow Jira Service Desk portal notification to use an Email Settings from Jira General Configurationn
            Amirul Ikhwan Omar (Inactive) made changes -
            Summary Original: Allow Jira Service Desk portal notification to use a Email from Settings from Jira General Configuration New: Allow Jira Service Desk portal notification to use an Email from Settings from Jira General Configurationn
            SET Analytics Bot made changes -
            Support reference count New: 1

              Unassigned Unassigned
              abinomar Amirul Ikhwan Omar (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: