Create new Jira Issue from Zendesk Ticket (Jira API V2)
| Source | Target | |
|---|---|---|
|
|
|
This integration selects new Zendesk tickets and imports them to Jira Cloud as issues.
Requirements
Jira connection must have specific settings:
- Environment must be set to Cloud, Jira Server connections are not supported;
- API Version must be set to Ver2.
How to Set Up
- Select or create connections: Zendesk connection for Source and Jira connection for Target.
- Provide the necessary information for the integration execution:
Open the import task
On the Mapping Definition of your import task, for the Issuetype_Id field, specify your Jira Issue type instead of Enter your Issue type (eg. Bug, Task or Epic), and also specify your Jira Project name instead of Enter your Project name....
For the Project_Id field, specify your Jira Project name instead of Enter your Project name....
For the Priority_Id field, specify the priority name for Jira Issue instead of Enter your priority name....
Important note: For Issue types other than Bug, Task or Epic, please remove mapping for this field. Otherwise, the integration will fail.
Save the task.
- Specify the schedule on which the integration will run automatically.
Tips
- To create Jira issues from specific new Zendesk tickets, configure filters in the task editor.
Frequently Asked Questions
What do I need to start this import?
Connect your source and target apps, review the prebuilt import setup, and run the template.
Can I change field mappings before importing?
Yes. You can review and modify mappings, filters, and other import settings before running the import.
Can this import run automatically on a schedule?
Yes. Import templates can run automatically based on your selected schedule.
What happens if some records fail during import?
Skyvia provides import logs and error details so you can review failed records and rerun the import if needed.
Do I need coding skills to use import templates?
No. Import templates are configured through Skyvia’s visual interface without coding.