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

Allow multiple Service Desks with distinct customer lists to use the same Email Address

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • Email - Incoming
    • 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.

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

      Scenario

      In certain cases, it may happen that:

      1. project SD1 has customers sd1cus1, sd1cus2
      2. project SD2 has customers sd2cusA, sd2cusB

      in other words, they have 2 totally different customer lists

      In such a case like this, the 2 projects should be allowed to use the same email address for Email requests, in which:

      • if sd1cus1 sends an email to this email address, JIRA detects that this customer belongs to SD1 only and will raise a request in SD1
      • if sd2cusA sends an email to this email address, JIRA detects that this customer belongs to SD2 only and will raise a request in SD2

      Suggestion

      When multiple SD projects meet the following requirements:

      1. each project has a distinct customer list in which no customer exists in more than one service desk
      2. public signup is not allowed and all projects have Request Security set to "Only people on my customers list"

      they should be allowed to use the same email address for Email requests.

          Form Name

            [JSDSERVER-4261] Allow multiple Service Desks with distinct customer lists to use the same Email Address

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Charlie Marriott added a comment -
            Atlassian Update – 1 March 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 March 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012346 ] New: JAC Suggestion Workflow 3 [ 3649755 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665876 ] New: JAC Suggestion Workflow [ 3012346 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324089 ] New: Confluence Workflow - Public Facing v4 [ 2665876 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Zul NS [Atlassian] made changes -
            Link New: This issue is duplicated by JSDSERVER-1169 [ JSDSERVER-1169 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052599 ] New: JSD Suggestion Workflow - TEMP [ 2324089 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048327 ] New: JSD Suggestion Workflow [ 2052599 ]

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: