We would really like a custom organistation field to be available in Views. We do have custom fields for different organizations, and customer chains, so we keep those in order by doing custom org. fields. It would be nice to see a view based on these custom fields.
Is this in development? If not, it's a requested feature.
A little follow up for post:
100%
I just ran into this issue - needing to populate/filter Organization fields in the ticket views.
Our Organizations are synced to Salesforce Accounts and we need to prioritize tickets according to a variety of Account fields (Churn Risk, SLA type, ARR, etc). As Salesforce is our source of truth for live account details, this is impossible to do at scale in Zendesk without visibility at the View level.
My team requires this feature as well.
Usecase:
Everytime a new end-user is created, we update some of their custom (not default) profile fields.
When these end-users create a ticket, we want to display these custom profile fields in our views.
Currently views can only add default fields and custom ticket fields, not custom profile fields of the requester.
This feature would be beneficial for my org as well.
The current work around we have in place is using org custom fields to execute a trigger that populates a custom ticket field which we include in the views, however this is only a workaround as it won't scale and we cannot currently hide these fields.
This is something my organisation would benefit from as well.
Looking forward to it being added at some point.
Any news on this??
+1
Would love this feature too! We're really making use of Organization custom fields and the views I need are far more complicated to make than they have to be.
Hey Jysk, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.
We are thinking through how to show more related data and this is great feedback. I have added it to the backlog and will use this information as we have these conversations. This means that we will think about adding it as a priority later in our planning cycle. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to prioritizing any one piece of feedback we receive in the community.
+1 need it.
+1 on this need, we use a customer Organization field to break down regions for example customer 1 is North America, customer 2 is APAC region etc. Would love to be able to make views based on regions that way.
+1 for us as well. We'd like to capture this information on each ticket for reporting (which team, department is submitting).
+1
We need this feature to allow for Account Representatives to easily see the tickets from all of their organizations. Presently they're needing to manually create views, impacting both our view count and their time.
+1 on this need, we use a customer Organization field to break down regions for example customer 1 is North America, customer 2 is APAC region etc. Would love to be able to make views based on regions that way.
I use this feature for the same reason. It was working ok now it appears to have stopped passing this information to the view. The Org field is still in my view but has no value although populated in the organisation.
Anyone else experiencing this?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
