Having an issue when sharing a ticket from Zendesk to JIRA. The sharing part works just fine, but it seems to always default to a project instead of the project I select from the dropdown.
Say I have 4 JIRA projects:
They all have mapping schemes setup, so that they appear in the Zendesk JIRA Sharing dropdown box. Well it seems that even if i select Project 4 as my choice, I am always getting my new JIRA ticket entered under Project 1. I believe it has something to do with the setting in JIRA on the Connections section under Zendesk Ticket Sharing Agreements. It is here on this screen that you have to pick a project, issue type, and Default Reporter, and what it looks like is happening is whatever project I select there (you can only choose a single project), is the default project when creating new JIRA tickets via Zendesk Share Ticket method.
How can I create a Zendesk Shared JIRA ticket that corresponds to the dropdown selection rather than always a "default" JIRA project?
Got an email from Zendesk helpdesk support that says it's fixed:
Thanks for your patience while we investigated the JIRA issues you've been experiencing. We discovered issues which occurred as a result of a change we made to ticketing last week and we have now fixed these issues. You may need to reload/refresh to see the changes, but all should be well now. However, please let us know immediately if this does not seem to be the case. Sorry again for any inconvenience this situation caused you and your team.
I am setting this ticket to solved for now, but please feel free to reply to this e-mail at any time to receive additional support on this issue - your reply will automatically reopen the ticket!
I did infact verify that this was fixed by creating a test ticket in Zendesk and sharing it with JIRA and selecting a project other than the "default" with an issue type that was not a "default" either.
I'm having the same issue. I've submitted a ticket to ZenDesk and they're looking in to it. I previously didn't have a default set for project and that was working fine. I did notice that JIRA pushed an update to our On Demand instance yesterday. Not sure if this issue is related to that update or not.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot