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

      Problem Definition

      As an agent, I would like to find out which organizations a customer belongs to even if they have chosen not to share the issue. This would allow me to run reports on organizations impacted by a particular issue.

      Suggested Solution

      I would like to be able to view an organization field which shows this information, or use automation to populate other fields based on this.

            [JSDSERVER-4903] As an Agent, I would like to see the organizations a customer belongs to

            While a bit clumsy solution but one way to work around this is to

            1. Create (for example) text based custom field that will hold the organization name
            2. Create automation that runs on issue create
            3. Create branch rule, "type of related issues" = current issue
            4. Create condition under this branching rule -> "User condition" -> "Check to perform" -> "Is in organization" = xxx
            5. In same branch after the condition add new action "Edit issue fields" and set the field created in step 1. to whatever the organization name is
            6. Create separate if-branch for each of the customer organizations

            What makes this approach clumsy is the fact that you need to manually create if-branch for each organization + the automation is not very effective performance-wise. So in massive service desks this is probably not an option.

            If you store the org info this way, you can use that as an additional filter for queues (if you have customer-specific queues).

            Artem Chatlikov added a comment - While a bit clumsy solution but one way to work around this is to Create (for example) text based custom field that will hold the organization name Create automation that runs on issue create Create branch rule, "type of related issues" = current issue Create condition under this branching rule -> "User condition" -> "Check to perform" -> "Is in organization" = xxx In same branch after the condition add new action "Edit issue fields" and set the field created in step 1. to whatever the organization name is Create separate if-branch for each of the customer organizations What makes this approach clumsy is the fact that you need to manually create if-branch for each organization + the automation is not very effective performance-wise. So in massive service desks this is probably not an option. If you store the org info this way, you can use that as an additional filter for queues (if you have customer-specific queues).

            David added a comment -

            If you have ScriptRunner, you can use some variation of this:

            import com.atlassian.servicedesk.api.organization.OrganizationsQuery;
            //import com.atlassian.jira.user.ApplicationUser;
            import com.atlassian.servicedesk.api.organization.OrganizationService;
            import com.atlassian.jira.component.ComponentAccessor
            import com.onresolve.scriptrunner.runner.customisers.PluginModule
            
            @PluginModule
            OrganizationService organizationService
            
            def user = ComponentAccessor.getUserManager().getUserByName("someuser")
            
            OrganizationsQuery organizationsQuery = organizationService.newOrganizationsQueryBuilder().build()
            organizationService.getOrganizations(user, organizationsQuery).getResults()
            

             

             

            David added a comment - If you have ScriptRunner, you can use some variation of this: import com.atlassian.servicedesk.api.organization.OrganizationsQuery; // import com.atlassian.jira.user.ApplicationUser; import com.atlassian.servicedesk.api.organization.OrganizationService; import com.atlassian.jira.component.ComponentAccessor import com.onresolve.scriptrunner.runner.customisers.PluginModule @PluginModule OrganizationService organizationService def user = ComponentAccessor.getUserManager().getUserByName( "someuser" ) OrganizationsQuery organizationsQuery = organizationService.newOrganizationsQueryBuilder().build() organizationService.getOrganizations(user, organizationsQuery).getResults()    

            This is a must to be able to properly handle reporter organization. Please implement it!

            Diego Losada added a comment - This is a must to be able to properly handle reporter organization. Please implement it!

            pacobarba added a comment -

            Please, this feature is essencial to view the organization from the reporter is, independently of the user marks or not share with his organization.

            pacobarba added a comment - Please, this feature is essencial to view the organization from the reporter is, independently of the user marks or not share with his organization.

            Felix Geis added a comment -

            Hi together,

            I was looking for this feature in the service desk REST documentation, which lead me to this suggestion.

            Is there any chance that this will be implemented?

             

            Felix Geis added a comment - Hi together, I was looking for this feature in the service desk REST documentation, which lead me to this suggestion. Is there any chance that this will be implemented?  

              Unassigned Unassigned
              khannon Keri Duthie (Inactive)
              Votes:
              76 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated: