OdooWiki OCA HUB

JIRA Connector Tempo (base)

connector_jira_tempo_base folder_open OCA/connector-jira open_in_new
Connector License: AGPL-3

This module provides base for building Tempo connectors.

auto_awesome What this module does

AI-generated from the code · Odoo 15.0

Adds a Tempo Timesheets section to the JIRA backend configuration and lets the connector fetch Tempo worklog details from JIRA.

This module is a technical building block for connecting Odoo with JIRA's Tempo Timesheets add-on. It does not add new menus or screens for everyday users; instead it extends the existing JIRA backend configuration form.

  • On the JIRA backend form, an "Advanced Configuration" page now contains a "Tempo" group with a note saying "Configure link with Tempo Timesheets". This is where the Tempo connection is set up.
  • Behind the scenes, when the connector reads a worklog from JIRA, it also asks Tempo Timesheets for the matching worklog data and stores it under a _tempo_timesheets key. If the worklog is not found in Tempo, the connector handles the missing record gracefully instead of failing.
  • The behaviour can be skipped by setting a context flag, so other modules can avoid the extra Tempo request when it is not needed.

The module touches the jira.worklog.adapter component and the jira.backend model. It depends on the main JIRA connector, so it only works when that connector is installed. No scheduled jobs, emails, or user-facing reports are added by this module.

Depends on

Models and fields (1)
  • jira.worklog.adapter · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 3 confirmed, 6 with no information of 9 versions.

Sources · Odoo 12.0

Confirmed on 2026-11-03 in branch 12.0 of OCA/connector-jira.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.