• 3
    • 24
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      I am finding it difficult to manage the customer organisations in JSD. Customers email through and get added to the customer list but we have to manually add them to an organisation. It would be ideal to have a rule in the organisation that can be turned off or on that includes a domain extension. If a customer emails through with the specified domain extension they are auto added to the organisation.

      AC:

      • Set a domain extension on the Organization
      • System reviews the emails sent through for a new customer and if the domain extension is matched to an organisation it adds the customer to that organisation

            [JSDCLOUD-4417] Add email domain to Customer Organisation

            BK Paton added a comment -

            Hey all, 

            Thanks for your votes and comments on this ticket. This ticket is a duplicate for JSDCLOUD-4519. I am going to close this issue (as it has the lesser votes of the two), and direct all future discussion into the other issue.

            Please add your vote, and any further feedback you wish to add (we will still have this issue for reference) over there.

            Cheers, 

            Ben.

            BK Paton added a comment - Hey all,  Thanks for your votes and comments on this ticket. This ticket is a duplicate for JSDCLOUD-4519 . I am going to close this issue (as it has the lesser votes of the two), and direct all future discussion into the other issue. Please add your vote, and any further feedback you wish to add (we will still have this issue for reference) over there. Cheers,  Ben.

            Petr AST added a comment -

            @ben In your case, your portal is open to everyone, i.e. can anyone write to the email address?
            After that, is it added to the organization?

            What to do with spam emails or blacklists such as service notifications? Is it possible to block them somehow?

            It seems to me that the most normal option would be to add support without disabling access to "only customers" of certain domains from which anyone can write a request.

            Petr AST added a comment - @ben In your case, your portal is open to everyone, i.e. can anyone write to the email address? After that, is it added to the organization? What to do with spam emails or blacklists such as service notifications? Is it possible to block them somehow? It seems to me that the most normal option would be to add support without disabling access to "only customers" of certain domains from which anyone can write a request.

            Thank you Ben

            Mark Anderson added a comment - Thank you Ben

            Ben added a comment - - edited

            Workaround but native functionality mentioned by someone in: https://jira.atlassian.com/browse/JSDCLOUD-4519

            Can be done with an automation 
            https://blog.codebarrel.io/set-organization-in-jira-service-desk-using-reporters-email-domain-e705be9d4717

            It edits the Organization field based on the reporter's email domain. 

            If the reporter and organization don't exist, it creates an organization with the email domain name. From the article it says it modifies the name, but not in my case. If you edit the organization name to the actual company name, and a new reporter of the same domain sends a request through, they are still added to the same organization. 

            Now the problem is if a customer has multiple domains. 

            EDIT: the renaming of the organization seems limited to .com domains (the functionality that the codebarrel article mentions). If you have domain.com.xx it creates the Organization name as "domain.com.xx."

            Ben added a comment - - edited Workaround but native functionality mentioned by someone in:  https://jira.atlassian.com/browse/JSDCLOUD-4519 Can be done with an automation  https://blog.codebarrel.io/set-organization-in-jira-service-desk-using-reporters-email-domain-e705be9d4717 It edits the Organization field based on the reporter's email domain.  If the reporter and organization don't exist, it creates an organization with the email domain name. From the article it says it modifies the name, but not in my case. If you edit the organization name to the actual company name, and a new reporter of the same domain sends a request through, they are still added to the same organization.  Now the problem is if a customer has multiple domains.  EDIT: the renaming of the organization seems limited to .com domains (the functionality that the codebarrel article mentions). If you have domain.com.xx it creates the Organization name as "domain.com.xx."

            Mark Cline added a comment -

            I have to say this is a pretty big deal for most companies.  When supporting large organizations, having to keep track of all the user email addresses is a problem. Not to mention the operational overhead of having to continuously add new users for a customer. 

            In addition, when telling your customers to send their requests to support@ email address and come to find out the tickets are not getting entered because its from a new or different employee at your customer organization creates support problems.  

            It is interesting that this has been in Gathering Interest for so long and is a pretty standard feature in most support help desks.

            Mark Cline added a comment - I have to say this is a pretty big deal for most companies.  When supporting large organizations, having to keep track of all the user email addresses is a problem. Not to mention the operational overhead of having to continuously add new users for a customer.  In addition, when telling your customers to send their requests to support@ email address and come to find out the tickets are not getting entered because its from a new or different employee at your customer organization creates support problems.   It is interesting that this has been in Gathering Interest for so long and is a pretty standard feature in most support help desks.

            Nearly four years people have wanted this feature and there has been zero interest from Jira in adding it. It's never happening.

            Dan McClintock added a comment - Nearly four years people have wanted this feature and there has been zero interest from Jira in adding it. It's never happening.

            Yes please.

            Jason Sweet added a comment - Yes please.

            Beh CS added a comment -

            This features is definitely a must. Please move on to build / add the feature asap. tq

            Beh CS added a comment - This features is definitely a must. Please move on to build / add the feature asap. tq

            Job Burg added a comment -

            More interest here to gather  

            Job Burg added a comment - More interest here to gather  

            Required feature for us.

             

            Rahul Sheth added a comment - Required feature for us.  

            spbarber added a comment -

            Stop gathering interest and add this feature as it will help with a large amount of customers like our company has to deal with.

            spbarber added a comment - Stop gathering interest and add this feature as it will help with a large amount of customers like our company has to deal with.

            I landed here after searching for this topic as I'm trying to add all customers from our internal email domain. While my 1800 is probably not as large as others, adding that many is going to be time intensive.

            Paul Mulvey added a comment - I landed here after searching for this topic as I'm trying to add all customers from our internal email domain. While my 1800 is probably not as large as others, adding that many is going to be time intensive.

            +1 - Adding email addresses by hand is a very manually-intensive process. This feature would greatly streamline work when a new Organization is added, or when employees are hired at the Organizations.

            Erik Brooks added a comment - +1 - Adding email addresses by hand is a very manually-intensive process. This feature would greatly streamline work when a new Organization is added, or when employees are hired at the Organizations.

            Stefan Haegglund added a comment - - edited

            I just voted for this feature to be included in future releases, personally I think it is very important. All other service desks we've evaluated have such a capability. Being a Jira Software fan, I'd really like the Jira Service Desk to equal the competition in this respect too. Lacking this capability could be a deal breaker for some. 

            Stefan Haegglund added a comment - - edited I just voted for this feature to be included in future releases, personally I think it is very important. All other service desks we've evaluated have such a capability. Being a Jira Software fan, I'd really like the Jira Service Desk to equal the competition in this respect too. Lacking this capability could be a deal breaker for some. 

            We have customers who are user for more than one organization. When a customerallready exists in Jira SD i'd like to add easlily an extra organization to the customer which is not possible.

            or easily add a customer to an organization which is not easy because the add customer pop-up doesn't recognize existing e-mailadresses

            Esther Witteveen added a comment - We have customers who are user for more than one organization. When a customerallready exists in Jira SD i'd like to add easlily an extra organization to the customer which is not possible. or easily add a customer to an organization which is not easy because the add customer pop-up doesn't recognize existing e-mailadresses

            where do you set a domain extension on the Organization?  I don't see any option to do that within the Add Organization screen.

            Steve Fitzgerald added a comment - where do you set a domain extension on the Organization?  I don't see any option to do that within the Add Organization screen.

            having the organization default based on the domain extension, however the organization field is also used to determines whether the issue is shared with the organization.   So, if a customer says they don't want to share it, it clears the organization and hence I don't know where they are from.  The problem stems from using that field for multiple purposes.

            Steve Fitzgerald added a comment - having the organization default based on the domain extension, however the organization field is also used to determines whether the issue is shared with the organization.   So, if a customer says they don't want to share it, it clears the organization and hence I don't know where they are from.  The problem stems from using that field for multiple purposes.

              7ad1551c39c0 BK Paton
              b7e970de282c Gavin McMillan
              Votes:
              110 Vote for this issue
              Watchers:
              62 Start watching this issue

                Created:
                Updated:
                Resolved: