With the Jira interface, you can transfer structures from Jira to ZEP. This allows Jira elements such as Spaces, Epics, and Issues to be used in ZEP as customers, projects, tasks, or tickets.
The Jira interface is a connection from Jira to ZEP. Jira remains the leading system for the transferred structures.
data direction: Jira -> ZEP
Connecting the Interface
You can find the Jira interface in ZEP under Administration > Interfaces > Interface Marketplace.
Select Jira there and click Add in the marketplace. You will then be guided through the booking process in the self-service tool. After booking, you can set up the interface in ZEP.
Prerequisites for Connecting Jira
To connect Jira with ZEP, you need:
Access to the Interface Marketplace in ZEP
Your Jira email address
A Jira API token
Data
The Jira interface offers flexible mapping. You define how Jira elements are used in ZEP.
Jira-Element | Mapping in ZEP |
Spaces | Projects or customers |
Epics | Projects or tasks |
Issues without Epic | tickets or tasks |
For Jira issues, the following information, among others, can be transferred to ZEP and used there:
Title or summary of the issue
Status
Priority
Creation date
Last modified date
Due date, if available
Assignment to a parent project or epic
Assignment of creator and assignee to employees in ZEP
Using Jira Worklogs in ZEP
Jira worklogs can be used for time tracking in ZEP. ZEP processes the worklog information from Jira and creates attendance entries in ZEP.
Settings in ZEP
During setup, you can define, among other things:
Customer number prefix for automatically created customers
Default department for automatically created projects
Default activity for time tracking
Typical Use case:
The interface is suitable if your team uses Jira as a central project or ticketing system and you want this structure to be available in ZEP for project work, tasks, tickets, or time tracking.