JIRA Field Mapping
I have a pretty basic setup, where I have 4 JIRA fields mapping to Zendesk, and only that direction. The fields are:
All of the Zendesk fields are "Text" type fields.
Behaviors I'm noticing:
- JIRA Ticket Number seems to be the most consistent in working
- JIRA Status is inconsistent, though no theme found on the ones that don't sync. It will be simple statuses like "Open" (which show fine in other instances). Not project specific either.
- Sprint never comes through
- Fix Version/s never comes through
Any thoughts on this?
-
Hi!
What kind of fields do you have set up on the Zendesk side? I usually do dropdowns for things like Status so I can action on them in Zendesk (i.e. reopen an On Hold ticket when Jira status goes to Released or Done).
-
Hi Heather Rommel, these are all text type fields. When mapping JIRA fields to Zendesk fields, you have to pick specific types depending on the JIRA field you're mapping (per this article - https://support.zendesk.com/hc/en-us/articles/4408825394458-Using-the-Jira-field-syncing-feature). So for instance, JIRA Status must map to either text or multi-line text.
-
Yep, though I use the dropdown for status because it works when you don't do multiple Jiras to 1 Zendesk. This way we can use triggers.
But to your point, your fields should be syncing! I wonder if Zendesk support should look into this. Unless your Zendesk tickets are in Closed status at the time it tries to sync? That would block it...
-
Hi Jake Warren
That is indeed a bit frustrating, especially if you can't put your finger on the reason why it works sometimes only.
It most probably has to do with the receiving end not receiving the data expected or running into an error while receiving/processing the info. Without any tracking of the data flow it would be difficult to provide any specific solution path.
Something that I can surely recommend is a specialised solution like Exalate. As it provides you with the ability to sync all of the required fields and much more. While also providing data/variable conversion if the recipient expects the data to arrive in a different format.
Also you can create status mappings to make sure you always set the right status on both sides even when using very different ticket flows.
Do let me know if you need any further info and/or support.
Kind regards,
-
Is it possible to map created field in Jira (when the ticket was created) to a Zendesk field? I don't see it on the field mapping screen in Jira.
-
Hey Emily! The "Created" field in Jira is not currently a field that can sync to Zendesk. For a full list of compatible fields, see Jira issue fields and compatible Zendesk ticket fields. If you can put the "Created" field value in Jira to a custom field in Jira, then you could potentially sync that to a custom Zendesk field.
-
Just to close the loop on my original issue, I worked with Zendesk support and they ended up making changes that fixed the issue. Our field mapping/syncing is now working for all fields I had in my original screenshot.
-
Hi Sabra,
Are you aware if there is work being done to allow the syncing of more fields between Jira / Zendesk? I have noticed several are missing, including:
- ID (Zendesk)
- Requester (Zendesk)
- Component (Jira)
-
Hey there! Haven't seen any so far but you may check the Zendesk Updates here for any new features that is or will be available.
Por favor, entrar para comentar.
9 Comentários