Organization Custom Fields for Ticket Organization instead of Requester Organization

Answered

4 Comments

  • Elaine
    Zendesk Customer Care

    Hi Travis,

    I think it is best if I see the report you're working on so I can better understand your concern. I will create a ticket on your behalf. Kindly wait for an email notification regarding this ticket. Cheers!

    0
  • Arno (EMEA Partner)

    Is there a solution to this issue. Is common, when serving large companies, that organization must be divided to multiple organizations, and ticket organization is more relevant than requester default organization.

    In reporting vise history also changes over time, if requesters default organization changes, and in reporting tickets wander from one organization to another. (EDIT: This happens only if you use Organization custom fields in filters, as this only possible via requester organization).

    Yes, this applies to situations where user's can belong to multiple organizations only. 

    I think I have seen another discussion about the same matter on some other thread, but could not locate it now.

    I could not figure out my self, how to be able to use ticket organization custom fields in filtering reports. I assumed, this is not possible yet.

     

     

    0
  • Travis Tubbs

    I had to email into Support for assistance on this. Sadly, they stated that this "is not possible and is currently an Explore limitation as the two data are currently found from two different types of data (tickets and organizations)."

    Their only recommendation was to create a custom ticket field that would be filled in automatically by a trigger. As you could imagine, this is not a viable workaround.

    As mentioned, there is a feature request thread on this (not sure where), but "for now, I have news that our Product team is currently not able to address this immediately and no target date has been set if in case this feature would be added into Explore."

    0
  • Arno (EMEA Partner)

    Thanks for the information. Appreciate you sharing this. Hopefully this will be solved soon. 

    0

Please sign in to leave a comment.

Powered by Zendesk