• 8
    • 9
    • 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.

      Issue Summary

      When an issue is created, can the organization the user belong to be added automatically to the Organization field?

      Suggestion

      Add the ability to create an Automation Rule that allows updating issue field Organization if the user is a member of the organization.

      Expected Behavior

      Feature does not exist yet.

            [JSDSERVER-4661] Auto Add Reporter's Organization

            Admin added a comment -

            Hi Felix,

            Not sure if you saw are post but we do offer this feature.

            We developed a plug-in to handle this situation, you can visit the market place to download and test:

            Organization Automation - https://marketplace.atlassian.com/apps/1219598/organizations-automation?hosting=server&tab=overview

            I was in the same boat as all of you and I know we needed to deal with this issue, because we really love using Jira, and I didn't want it to be a deal breaker for our company.

            We also developed a companion plug-in that will match-up users based on their domain, meaning when they submit a ticket, i.e. when the user sends an email, example: kelly@example.com and I have an organization with that same domain in my Jira setup, it will map that users to that organization... I hope you find them helpful.

            Reply-to Mail Handler https://marketplace.atlassian.com/apps/1219595/service-desk-reply-to-mail-handler?hosting=server&tab=overview

            Any questions please do not hesitate to contact me.

            I hope you all find these as helpful as we do!

            Thank you,

            Kelly

            Admin added a comment - Hi Felix, Not sure if you saw are post but we do offer this feature. We developed a plug-in to handle this situation, you can visit the market place to download and test: Organization Automation  -  https://marketplace.atlassian.com/apps/1219598/organizations-automation?hosting=server&tab=overview I was in the same boat as all of you and I know we needed to deal with this issue, because we really love using Jira, and I didn't want it to be a deal breaker for our company. We also developed a companion plug-in that will match-up users based on their domain, meaning when they submit a ticket, i.e. when the user sends an email, example:  kelly@example.com  and I have an organization with that same domain in my Jira setup, it will map that users to that organization... I hope you find them helpful. Reply-to Mail Handler  -  https://marketplace.atlassian.com/apps/1219595/service-desk-reply-to-mail-handler?hosting=server&tab=overview Any questions please do not hesitate to contact me. I hope you all find these as helpful as we do! Thank you, Kelly

            The addition of a link between the user and its organization would save us so much time with the creation of an automated rule that edits the organization based on the reporter.

            Félix Goulet added a comment - The addition of a link between the user and its organization would save us so much time with the creation of an automated rule that edits the organization based on the reporter.

            Fusic Jira added a comment -

            whould be sad if the commuity has to pay for a feature that should have been implemented from the beginning..

            If I assign a Customer to a Company/Organisation, and display the Company/Organisation field within a issue overview, of course I would expect that the Company/Organisation field gets populated automatically with the Company/Organisation the Customer is assigned to.

            It just does not make any sense to be able to select another Company/Organisation the customer is not assigned to, but i think this is a deeper issue, Jira not having a fix customer database that all AddOns are able accessing nor beeing able to create a fix link between a customer and his Company/Organisation.

            E. g. we need additional AddOns to be able to manage Customers and Company/Organisation, but those AddOns are not able to work with the Data comming from JSD but create another set with its own Customer and Company/Organisation information.... So far, if Customerinformation changes, we need to adjust this in JSD and 2 other AddOns as they are unable to share the Customer and Company/Organisation information. 

            could be sooo nice and easy....

            Fusic Jira added a comment - whould be sad if the commuity has to pay for a feature that should have been implemented from the beginning.. If I assign a Customer to a Company/Organisation, and display the Company/Organisation field within a issue overview, of course I would expect that the Company/Organisation field gets populated automatically with the Company/Organisation the Customer is assigned to. It just does not make any sense to be able to select another Company/Organisation the customer is not assigned to, but i think this is a deeper issue, Jira not having a fix customer database that all AddOns are able accessing nor beeing able to create a fix link between a customer and his Company/Organisation. E. g. we need additional AddOns to be able to manage Customers and Company/Organisation, but those AddOns are not able to work with the Data comming from JSD but create another set with its own Customer and Company/Organisation information.... So far, if Customerinformation changes, we need to adjust this in JSD and 2 other AddOns as they are unable to share the Customer and Company/Organisation information.  could be sooo nice and easy....

            Hello @all,

            We developed a plug-in to handle this situation, you can visit the market place to download and test:

            Organization Automation - https://marketplace.atlassian.com/apps/1219598/organizations-automation?hosting=server&tab=overview

            I was in the same boat as all of you and I know we needed to deal with this issue, because we really love using Jira, and I didn't want it to be a deal breaker for our company.

            We also developed a companion plug-in that will match-up users based on their domain, meaning when they submit a ticket, i.e. when the user sends an email, example: kelly@example.com and I have an organization with that same domain in my Jira setup, it will map that users to that organization... I hope you find them helpful.

            Reply-to Mail Handler https://marketplace.atlassian.com/apps/1219595/service-desk-reply-to-mail-handler?hosting=server&tab=overview

            Any questions please do not hesitate to contact me.

            I hope you all find these as helpful as we do!

            Thank you,

            Kelly

            kelly_grills added a comment - Hello @all, We developed a plug-in to handle this situation, you can visit the market place to download and test: Organization Automation  -  https://marketplace.atlassian.com/apps/1219598/organizations-automation?hosting=server&tab=overview I was in the same boat as all of you and I know we needed to deal with this issue, because we really love using Jira, and I didn't want it to be a deal breaker for our company. We also developed a companion plug-in that will match-up users based on their domain, meaning when they submit a ticket, i.e. when the user sends an email, example:  kelly@example.com  and I have an organization with that same domain in my Jira setup, it will map that users to that organization... I hope you find them helpful. Reply-to Mail Handler  -  https://marketplace.atlassian.com/apps/1219595/service-desk-reply-to-mail-handler?hosting=server&tab=overview Any questions please do not hesitate to contact me. I hope you all find these as helpful as we do! Thank you, Kelly

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              140 Vote for this issue
              Watchers:
              70 Start watching this issue

                Created:
                Updated: