OdooWiki OCA HUB

JIRA Connector - Service Desk Extension

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

This module add support with jira servicedesk

auto_awesome What this module does

AI-generated from the code · Odoo 17.0

This module extends the JIRA connector to support JIRA Service Desk organizations. It lets you import organizations from JIRA, link them to Odoo projects, and automatically route tasks and worklogs to the correct project based on the organization.

This module adds support for JIRA Service Desk organizations to the JIRA connector. It introduces a new 'Jira Organization' model that stores organizations imported from JIRA. On the JIRA backend configuration, you get a new 'Organizations' tab where you can run an import to fetch all organizations from JIRA, and a button to configure the custom field that holds the organization on JIRA issues.

When linking a JIRA project to an Odoo project, a new step 'Link Organizations' appears in the linking wizard. You can select one or more organizations to associate with the project. The module then ensures that tasks and worklogs are only imported into that Odoo project if the task's organization matches the project's organizations. If no exact match is found, it falls back to a project linked without organizations; if none exists, the task is ignored.

The module also adds a 'Service Desk' project type and a field for the customer portal ID, which is used to build direct links to JIRA Service Desk issues. These links are shown on analytic lines and their JIRA counterparts. Additionally, a constraint prevents linking the same JIRA project to multiple Odoo projects with the same set of organizations.

Depends on

connector_jira
Models and fields (13)
  • jira.backend · extends an existing modelorganization_ids (Organizations), organization_field_name (Organization Field)
  • jira.organization · new modelname, backend_id, project_ids
  • project.link.jira · extends an existing model
  • jira.project.binder · extends an existing model
  • jira.project.project · extends an existing modelservicedesk_customer_portal_number (Service desk customer portal ID)
  • account.analytic.line · extends an existing modeljira_servicedesk_issue_url (Original JIRA service desk issue Link)
  • jira.project.base.mixin · extends an existing modelorganization_ids (Organization(s) on Jira)
  • jira.organization.mapper · new model
  • jira.organization.adapter · new model
  • jira.task.project.matcher · extends an existing model
  • jira.account.analytic.line · extends an existing modeljira_servicedesk_issue_url (Original JIRA service desk issue Link)
  • jira.organization.from.task · new model
  • jira.organization.batch.importer · new model

Text generated by AI (DeepSeek) from reading the Odoo 17.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 17.0

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

terminal Installation and usage

OCA documentation · Odoo 17.0

Usage

Source · Odoo 17.0

Setup

A new button is added on the JIRA backend, to import the organizations of JIRA. Before, be sure to use the button "Configure Organization Link" in the "Advanced Configuration" tab.

Features

Organizations

On Service Desk, you can share projects with Organizations. You may want to use different Odoo projects according to the organizations. This is what this extension allows.

Example:

  • You have one Service Desk project named "Earth Project" with key EARTH
  • On JIRA SD You share this project with organizations Themis and Rhea
  • However on Odoo, you want to track the hours differently for Themis and Rhea

Steps on Odoo:

  • Create a Themis project, use the "Link with JIRA" action with the key EARTH
  • When you hit Next, the organization(s) you want to link must be set
  • Repeat with another project for Rhea

If the project binding for the synchronization already exists, you can still edit it in the settings of the project and change the organizations.

When a task or worklog is imported, it will search for a project having exactly the same set of organizations than the one of the task. If no project with the same set is found and you have a project configured without organization, the task will be linked to it.

This means that, on Odoo, you can have shared project altogether with dedicated ones, while you only have one project on JIRA.

  • Tasks with org "Themis" will be attached to this project
  • Tasks with org "Rhea" will be attached to this project
  • Tasks with orgs "Themis" and "Rhea" will be attached to another project "Themis and Rhea"
  • The rest of the tasks will be attached to a fourth project (configured without organizations)

No verified information in OCA: Installation, Configuration.

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.