JIRA-Zendesk integration add sync of custom field of type 'Version picker (multiple versions)'

Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.]. (2-3 sentences)

I would like to synchronize a custom field of type 'Version picker (multiple versions)' from JIRA to Zendesk so that we can use the data in Zendesk in a macro for replying to tickets. This will be used by our R&D team and product managers to update customers on the ‘expected version’ for a fix or feature. This works for the default JIRA ‘Fix version/s’ field but not for a custom field with the same configuration.

What problem do you see this solving? (1-2 sentences) 

Customers would like to be informed if a bugfix of feature request reported via Zendesk is planned for a specific release/version. We use a JIRA for planning and if we ‘promise’ or plan a fix or feature request for a new version then we fill the custom field ‘Expected version’. In that case we can also inform the customer(s) via Zendesk. It would save time if we could sync the value from the ‘expected version’ field to a Zendesk field which we then can use in a macro to reply to tickets.  

When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business? (3-4 sentences)

Every two weeks we do our sprint planning and would lile to use this to communicate to our customers about upcoming bugfixes and features.

Are you currently using a workaround to solve this problem? (If yes, please explain) (1-2 sentences)

Yes, we have to manually look up the data and fill it in the text of the macro in Zendesk. 

What would be your ideal solution to this problem? How would it work or function? (1-2 sentences)

I would like to see the option added to the JIRA-Zendesk integration to configure synchronization of custom fields of type 'Version picker (multiple versions)'. This should work the same as the default ‘Fix version/s’ JIRA field.