Vitalii Petrus

Hi,

We use “Zendesk Support for Jira” app (more details in “Using the Zendesk Support for Jira integration” article).

We want to to setup sync of the linked Jira Issue ID of the required issue type to the appropriate txt field in Zendesk, i.e. while having several fields on Zendesk side that can be synced from Jira there is no way on how to divide which issue type ID should be passed to which Zendesk issue type field.

For now it is possible to perform “many to one” sync and it add a few ID-s into one txt field in Zendesk ( BTW, according to Zendesk Team, further checking with JIRA experts, the many:1 sync (or 1:many) is generally not supported and known to break the field mapping feature):

What we need is to pass specific issue type ID to the specific TXT custom field in Zendesk (could be 1to1 or many to 1 if several issues of the same issue type are linked):

It is done manually now but need to be automated.
So the Zendesk Support for Jira App needs to have ability to sync fields by its properties such as issue type (additional condition is required).

Thank you in advance!

Hello Team,

We use “Zendesk Support for Jira” app (more details in “Using the Zendesk Support for Jira integration” article).
We have a Custom field "QA/Support contact" in Jira.
It has a User Picker (single user) type in Jira.
We need to display this field in Zendesk Support.
But this field is not compatible with the Jira App in Zendesk Support.

We aim to set the "QA/Support contact" field during Jira ticket creation in Zendesk and sync it with Jira afterwards. 

Meanwhile the default assignee field is also of  "User Picker" (single user) type and is  available to be set from Zendesk Support, the custom fields of this type are not supported yet.
Please add support of Jira custom "User Picker" (single user) type field in Zendesk Support for Jira used for Jira <- -> Zendesk integration.
Thanks!

Hi James (James Peterson - Eastern Logic),
Thank you for your comment.
To update the required field in Organization using a webhook is not a problem (mainly).
The problem is to make this webhook run under the proper condition (e.g. if Particular Organization field was changed) →Notify by email/webhook/whatever i.e. the same behaviour as we have for some ticket fields
 

Hi 이지훈(maclaude) ,

Thank you for your follow-up!
The suggested webhook is not what I need. Because there is no condition under which the action that would run this webhook, will fire at the moment when Org field is changed.
The expected outcome for me is a condition in Automation/trigger which can be used for custom fields in the Organization, e.g. IF Organization>Some Custom Field →“Changed” is true, action to fire a notification to slack channel/email will be run via Notify by

And this  "Is Changed" condition can be applicable to any field type (date, checkbox, text, etc. ).
I believe, the same expectation was announced in the initial request from Stephanie McIntyre
Thank you in advance!

BR,
Vitalii

Since “the organization is ignored for agents” the Matching users page from User segment shows all users from the matched organization (Filter by organizations) + all agents which is very tricky to see in Matching users 100+ records.

It is hard to detect if there are no random users who do not belong to the filtered organization because when you follow “View all matching users” page there is no filter, there is no sorting by organization to check if all matched users are correct, so you need to click all pages to make sure all is okay. 

At least filters by role, organization, tags are required + sorting by role or organization (tag optional).

+1 to get this option in Zendesk

+1
We need to know when specific fields are changed in Organizations because their fields values impact other flows and processes in systems not integrated with Zendesk, e.g. monitoring systems, etc.

Hello,
Arianne Batiles 
I can create users without email from the agent interface in the organization like
https://{$domain}.zendesk.com/agent/users/{$org.ID}/organization/users
I didn't find a feature request to make email field be mandatory in this case on the admin level. Is there any request or is it planned to be implemented?

+1

+1