Jira Integration for transferring projects and tickets to ZEP
Your team works in Jira — ZEP takes over the structure. With the ZEP Jira integration, Spaces, Epics and Issues automatically flow into ZEP as projects, operations and tickets. Jira remains the leading system, ZEP handles time tracking and project controlling.

More than 3,000 companies rely on ZEP




































Benefits of the Jira Integration
From Jira structure to billable project time — without manual rework.
Map Jira structures flexibly in ZEP
- Spaces are created as customers or projects in ZEP
- Epics are transferred as projects or operations
- Issues without an Epic appear as tickets or operations — depending on your configuration
Transfer issue data completely
- Title, status, priority, creation and due date flow directly into ZEP
- Creator and assignee are automatically matched to the correct employees in ZEP
- Assignment to the parent project or Epic is retained
Use Jira worklogs for time tracking
- Worklogs recorded in Jira are evaluated by ZEP and processed as attendance entries
- No duplicate time tracking — Jira and ZEP stay in sync
- Time data is available directly for project controlling and invoicing in ZEP


ZEP in vollem Funktionsumfang 14 Tage kostenlos testen
How to configure the Jira interface

Connect Jira with ZEP
The Jira interface can be found in ZEP under Administration > Interfaces > Interface Marketplace. Select Jira and click "Add" — you will be guided automatically through the booking process. To connect, you will need your Jira email address and a Jira API token.
After setup, you define how Jira elements should be mapped in ZEP.
All setup details can be found in our Help Center.

FAQ
Frequently asked questions and answers about the ZEP Jira integration.
Who is the Jira integration with ZEP suitable for?
The integration is suitable for consulting and IT service companies that use Jira for project management and issue tracking and ZEP for time tracking and invoicing. Teams that want to keep Jira as their central system for project structures while building clean project time tracking and commercial control in ZEP — without having to maintain structures twice — benefit particularly from this.
What is the difference between Jira and ZEP — and why do I need both?
Jira is a project management and issue tracking system that helps teams plan, track and manage tasks. ZEP is a project time tracking and invoicing platform for service providers. The integration connects both worlds: Jira structures flow into ZEP, where time can be recorded precisely, projects controlled and services invoiced.
Does the Jira synchronization work in both directions?
No, the interface transfers data exclusively from Jira to ZEP. Jira remains the leading system for project structures and issues. Changes in ZEP are not transferred back to Jira. This clear directional separation ensures that Jira is maintained as the single source of truth for your project management.
Which Jira elements are transferred to ZEP?
The ZEP Jira interface transfers Spaces, Epics and Issues from Jira to ZEP. Spaces can be mapped as customers or projects, Epics as projects or operations, and Issues without an Epic as tickets or operations. Additionally, issue details such as title, status, priority, due date, as well as creator and assignee are transferred.
How can project time tracking be combined with Jira and ZEP?
With the ZEP Jira integration, Jira structures are automatically transferred to ZEP — Spaces, Epics and Issues appear there as projects, operations or tickets. Employees can book their time in ZEP directly against the structures imported from Jira. In addition, Jira worklogs can be evaluated and processed as attendance entries in ZEP — without duplicate recording.


