Fibery’s Zendesk integration doesn’t pull in the Brand field, and surprisingly, it also doesn’t include Ticket Numbers.
We use Zendesk to manage support for multiple brands within a single instance, which keeps everything well-organized and isolated by brand.
Adding support for these fields would be incredibly useful to:
Easily reference tickets by their actual Zendesk ticket #
Filter and organize tickets in Fibery by brand
Since Zendesk natively supports multiple brands, having these fields available in Fibery would make a big difference in keeping workflows complete and structured.
Nice! How quickly could it be added? I’m wondering if we should hold off on creating the formula field that extracts the ticket number from the url, if this field will be available soon.
What’s your take on the brand field? I’ve found a potential workaround, but it would require setting up an automation in Zendesk to apply a tag we could then use in Fibery. Ideally, I’d like to avoid relying on external automations where possible.
Another issue is when attaching a ticket to another database — it defaults to displaying by the name field. This is a problem since names aren’t unique in Zendesk.
Example from our setup:
I’m trying to link a ticket that reported an issue to its corresponding bug in our Bugs database.
As you can see, searching by name isn’t helpful here, since multiple tickets share the same name:
It would be helpful if we could choose which field is displayed in the relation view — like the ticket number or any other field that makes it easier to distinguish between records.
At the moment “subject” is used as name. I have some doubts whether it’s a good idea to put id to the name, but I can definitely expose additional “subject” field so later you can just use formula for name field and configure it like [subject] + [zendesk_id]
The ticket numbers are now being synced.
