# Usability and Performance Issues with Zendesk Integration

**URL:** <https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576>\
**Category:** Bugs & Issues\
**Created:** [April 24, 2021, 12:27pm UTC](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576 "2021-04-24T12:27:40Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\
**Post date:** [May 17, 2021, 2:33pm UTC](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576/21 "2021-05-17T14:33:40Z")

</div>

> [@rothnic](#):
>
> this seemed to be a timeout driven from the number of users/tickets being synced

Hm…this looks like a Zendesk issue for me then since we don’t refresh access token and the same one is used for time-outed requests and successful ones

> [@rothnic](#):
>
> Was there any thought around using Types for anything else that is synced?

If you have other types in mind that are worth importing please share🙏🏻We’ll try to add them as soon as possible

> [@rothnic](#):
>
> So, there is only a single field, `Created By`

Unfortunately Fibery imports enum fields as plain text right now. But this is something that can be improved in next iterations.

> [@rothnic](#):
>
> I’m also noticing that only “System” fields are currently being synced

User fields will be added in next iterations. Will keep you updated

---

<div class="post-metadata">

**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\
**Post date:** [May 17, 2021, 3:03pm UTC](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576/22 "2021-05-17T15:03:48Z")

</div>

> [@misha](#):
>
> Unfortunately Fibery imports enum fields as plain text right now. But this is something that can be improved in next iterations.

If enum fields can only be plain text, then I’d just suggest either fixing that limitation at some point or allowing users to utilize Types for each of the dropdown fields if desired. In other words, if they want the text to show up as a Type allow it, but still sync the data if they don’t.

Otherwise, I think it seems to be getting all the content of the tickets flowing through now.

---

<div class="post-metadata">

**Author:** ![misha](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/misha/32/12041_2.png) [@misha](https://community.fibery.io/u/misha)\
**Post date:** [May 26, 2021, 8:51am UTC](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576/23 "2021-05-26T08:51:55Z")

</div>

> [@rothnic](#):
>
> I’m also noticing that only “System” fields are currently being synced. Severity doesn’t show up for me

FYI: support of custom ticket fields has been added recently. Severity should appear after next sync

---

<div class="post-metadata">

**Author:** ![rothnic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/rothnic/32/1850_2.png) [@rothnic](https://community.fibery.io/u/rothnic)\
**Post date:** [May 26, 2021, 1:59pm UTC](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576/24 "2021-05-26T13:59:45Z")

</div>

> [@misha](#):
>
> Severity should appear after next sync

Thanks, yeah it looks to be coming through now.

[Previous page](https://community.fibery.io/t/usability-and-performance-issues-with-zendesk-integration/1576.md?page=1)