-------
MOCO + Jira
Connect MOCO Business Focus with Jira Tasks & Tickets
Jira is a task management tool that is particularly popular among developers and agile teams. MOCO offers an optimal synergy. There are various integration options:
1. Integration via the MOCO Browser Extension
From MOCO
With the MOCO extension, you can directly record time spent on Jira issues, Kanban boards, and overviews in MOCO during daily work—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
(English image not yet available)
Note on Permissions/Data Protection
The MOCO Browser Extension needs to integrate into various pages, requiring certain permissions. We only read the recorded times from MOCO and send only the information necessary for creating time entries to MOCO. We do not collect or use any other data. For transparency, we have published the code from the start: https://github.com/hundertzehn/mocoapp-browser-extension
(English image not yet available)Note on Permissions/Data Protection
The MOCO Browser Extension needs to integrate into various pages, requiring certain permissions. We only read the recorded times from MOCO and send only the information necessary for creating time entries to MOCO. We do not collect or use any other 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 adjusted as an endpoint in the extension settings. The extension itself is open source, so it could alternatively be built independently.
(English image not yet available)
(English image not yet available)2. Jira → MOCO Worklog Synchronisation
From Mindset.Swiss
This workflow, created for the self-hosted version, automatically synchronises all newly created or updated worklogs from Jira with the MOCO time tracking system daily. Mindset.Swiss has developed the n8n solution and provides you with 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 the remote_id = Jira-WorklogId are retrieved.
5. Both data sources (Jira + MOCO) are merged and analysed: Is there already an entry in MOCO? → Update. Is there no entry? → Create a new entry in MOCO.
6. If no MOCO service exists for the worklog author, it is automatically created.
7. Finally, the activity is created or updated on the Jira issue in MOCO with these details: project assignment, comment, date, time spent, remote link.
Mindset.Swiss will send you the JSON for the workflow if you contact them via the contact form with the note "Jira → MOCO Worklog Synchronisation".
This workflow, created for the self-hosted version, automatically synchronises all newly created or updated worklogs from Jira with the MOCO time tracking system daily. Mindset.Swiss has developed the n8n solution and provides you with 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 the remote_id = Jira-WorklogId are retrieved.
5. Both data sources (Jira + MOCO) are merged and analysed: Is there already an entry in MOCO? → Update. Is there no entry? → Create a new entry in MOCO.
6. If no MOCO service exists for the worklog author, it is automatically created.
7. Finally, the activity is created or updated on the Jira issue in MOCO with these details: project assignment, comment, date, time spent, remote link.
Mindset.Swiss will send you the JSON for the workflow if you contact them via the contact form with the note "Jira → MOCO Worklog Synchronisation".
