MOCO Integration Jira

« Zurück zu den Integrationen

Entwicklung & Support
Browser-Extension
MOCO

MOCO

-------

Jira

Task Management

MOCO + Jira

Connect MOCO Business Focus with Jira Tasks & Tickets

Jira is a task management tool popular among developers and agile teams. It integrates seamlessly with MOCO, offering various integration options:

1. Integration via the MOCO Browser Extension

From MOCO
With the MOCO extension, you can track time spent on Jira issues directly from the Kanban board and overview without switching to MOCO. The ticket ID is also part of the timesheet (csv/xlsx).

Setting Up the Connection

» In the video, Tobias demonstrates the setup starting at minute 1:00
Video Browser Extension Erweiterung Zeiterfassung MOCOEnglish image not yet available...
Note on Permissions/Privacy
The MOCO Browser Extension requires certain permissions to integrate with various pages. We only read the times entered in MOCO and send only the information necessary for creating time entries to MOCO. We do not collect or use any additional data. For transparency, we have published the code from the start: https://github.com/hundertzehn/mocoapp-browser-extension 

Self-hosted Jira 

Self-hosted Jira can be configured as an endpoint in the extension settings. The extension itself is open source, so it can alternatively be built independently.
Jira mit ERP Agentursoftware MOCO verbindenEnglish image not yet available...

2. Time Tracking Sync Jira – MOCO

By Scolution
Alternatively, the integration developed by MOCO client Scolution (an IT consulting company from Schwäbisch Hall) is available. 
  • Browser-independent
  • For Jira Cloud and Jira Server
  • Jira time tracking is synced with MOCO
  • Custom fields and automatic description generation 

3. Jira → MOCO Worklog Synchronization

By Mindset.Swiss
This workflow, created for the self-hosted version, automatically syncs all newly created or updated worklogs from Jira with the MOCO time tracking system daily. Mindset.Swiss developed the n8n solution and provides the JSON for the workflow.

Overview of the Process:
1. A daily trigger (midnight) starts the workflow.
2. Updated worklogs from the last 15 days are retrieved from Jira.
3. Additional issue details (type, description, author, etc.) are fetched from Jira for each worklog.
4. Simultaneously, existing MOCO activities with remote_id = Jira-WorklogId are retrieved.
5. Both data sources (Jira + MOCO) are merged and analyzed: Is there already an entry in MOCO? → Update. No entry? → Create new in MOCO.
6. If no MOCO service exists for the worklog author, it is automatically created.
7. Finally, the activity with these details is created or updated on the Jira issue in MOCO: project assignment, comment, date, time spent, remote link.

Download the JSON for the workflow via this link

4. Additional Workflows with MOCO + Jira

Zapier (no programming skills required)

Make (programming skills beneficial)

API (with programming skills)

30 days free trial

Account ready to go immediately. No payment details required.