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

Add the ability to configure multiple email handlers for a single Service Desk project

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

      Atlassian Update – 18 February 2022

      Hi everyone,

      Thank you for your interest in this issue, and to those customers who tried out the beta version of this feature and shared their feedback!

      We have now shipped multiple email channel support for Jira Service Management Data Center 4.22.

      You can now configure as many dedicated email channels as you need for better communication with customers. Their emails will turn into requests or comments, personalising and speeding up the process.

      Learn more about email channels.

      Kind regards,

      Charlie

      Jira Service Management, Data Center & Server

      Problem: A single Service Desk may have many Request Types yet only one email account can be associated with one Request Types meaning users have to use the GUI to create a Service Desk Request.

      Suggestion(s): Allow multiple email address to be associated with a single Service Desk, multiple Request Types to be associated with a single email address, or holistically associate the Service Desk with one email.

          Form Name

            [JSDSERVER-798] Add the ability to configure multiple email handlers for a single Service Desk project

            eb made changes -
            Comment [ his is eactly feature we need on cloud instance to be able to manage ESM project.

            we have only one ESM project (internal one) and need ad an incoming (aliased email) to receive external "job application". like [job@company.com|mailto:job@company.com]

            then we need another email to contact board member like  : [direction@company.com.|mailto:direction@company.com.]

            how can we workaround this and can this be released on Jira cloud?

             

            what you thinkg Craig Shannon ?
            h4.   ]
            eb made changes -
            Comment [ this is eactly feature we need on cloud instance to be able to manage ESM project.

            we have only one ESM project (internal one) and need ad an incoming (aliased email) to receive external "job application". like [job@company.com|mailto:job@company.com]

            then we need another email to contact board member like  : [direction@company.com.|mailto:direction@company.com.]

            how can we workaround this and can this be released on Jira cloud? ]
            Rodrigo Martinez made changes -
            Remote Link Original: This issue links to "JSDS-7001 (Bulldog)" [ 500567 ] New: This issue links to "JSMDC-7001 (JIRA Server (Bulldog))" [ 500567 ]
            ajaiswal made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 732986 ]
            Charlie Marriott made changes -
            Remote Link Original: This issue links to "Page (Confluence)" [ 525052 ]
            ajaiswal made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 712039 ]
            Alex Cooksey made changes -
            Link New: This issue resolves JSDSERVER-6998 [ JSDSERVER-6998 ]
            Craig Shannon made changes -
            Attachment New: image-2022-02-24-11-22-21-732.png [ 417346 ]
            Craig Shannon made changes -
            Attachment New: Screen Shot 2022-02-24 at 9.27.17 am.png [ 417345 ]
            Charlie Marriott made changes -
            Description Original: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-798].
            {panel}
            {panel:title=Atlassian Update – 2 July 2021|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Hi everyone,

            Thank you for your interest in this issue.

            We are excited to let you know that the [JSM Data Center 4.18 release|https://confluence.atlassian.com/servicemanagement/jira-service-management-4-18-x-release-notes-1072467369.html#JiraServiceManagement4.18.xreleasenotes-multipleemails] includes a beta version of upcoming multiple email channel support for JSM.

            We have been working on increasing the number of email channels you can configure in Jira Service Management so your customers can send emails to different addresses and get them turned into requests or comments. This will let you use different channels for different request types, or just have more personalised email addresses for your customers.

            Please refer to [this document|https://confluence.atlassian.com/jiracore/adding-multiple-email-channels-for-creating-requests-1063178702.html] for details on how to enable and setup this feature. We would also love your feedback, which you can share via [this survey|https://forms.gle/yiLzhsWEJm7Ks6Mq6].

            We look forward to hearing how you go with the beta version of multiple email channel support for JSM!

            Kind regards,

            Charlie Marriott

            Jira Service Management, Server & Data Center
            {panel}
            *Problem*: A single Service Desk may have many _Request Types_ yet only one email account can be associated with one _Request Types_ meaning users have to use the GUI to create a Service Desk Request.

            *Suggestion(s)*: Allow multiple email address to be associated with a single Service Desk, multiple _Request Types_ to be associated with a single email address, or holistically associate the Service Desk with one email.
            New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for {*}JIRA Service Desk Server{*}. Using {*}JIRA Service Desk Cloud{*}? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-798].
            {panel}
            {panel:title=Atlassian Update – 18 February 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Hi everyone,

            Thank you for your interest in this issue, and to those customers who tried out the beta version of this feature and shared their feedback!

            We have now shipped multiple email channel support for [Jira Service Management Data Center 4.22|https://confluence.atlassian.com/servicemanagement/jira-service-management-4-22-x-release-notes-1114802916.html#JiraServiceManagement4.22.xreleasenotes-requests].

            You can now configure as many dedicated email channels as you need for better communication with customers. Their emails will turn into requests or comments, personalising and speeding up the process.

            [Learn more about email channels|https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html].

            Kind regards,

            Charlie

            Jira Service Management, Data Center & Server
            {panel}
            {*}Problem{*}: A single Service Desk may have many _Request Types_ yet only one email account can be associated with one _Request Types_ meaning users have to use the GUI to create a Service Desk Request.

            {*}Suggestion(s){*}: Allow multiple email address to be associated with a single Service Desk, multiple _Request Types_ to be associated with a single email address, or holistically associate the Service Desk with one email.

              cmarriott Charlie Marriott
              jgiles@atlassian.com James Giles IV (Inactive)
              Votes:
              601 Vote for this issue
              Watchers:
              300 Start watching this issue

                Created:
                Updated:
                Resolved: