# Implementation JIM-304 - Centralize logging of Jira import jobs

Project: Stream Jira to OpenProject data Migrator
Status: review approved
URL: https://community.openproject.org/work_packages/JIM-304

## OPEN POINTS

_No work packages_

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Designer |  |
| Developers | Alfonso Mancilla |

## Technical details

| Attribute | Value |
| --- | --- |
| Target versions | 18.1.0 |
| Module |  |
| Requires doc change | No |

## Belongs to

_No work packages_

## Previous chunks

_No work packages_

## Next chunks

_No work packages_

## Estimates

| Attribute | Value |
| --- | --- |
| Work |  |

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| % Complete |  |
| Category |  |
| Sprint | Sprint 18.11.-24.11.2026 |
| Backlog bucket |  |
| Priority | Medium |
| List |  |
| Pull preview |  |
| Labels |  |

## Description

At the moment every import job builds its own log tags and writes its own lifecycle lines. This is repeated across 27 jobs and must be copied into each new job. The idea is to use the lifecycle callbacks from our job related gems, to de-duplicate the shared logs.

**Acceptance criteria:**

*   All import jobs report start, completion and failure the same way.
    
*   Every line logged while an import job runs carries the import&#x27;s context without the job adding it.
    
*   A new import job gets this by declaring what it imports.
    

**Technical notes:**&nbsp;

*   A shared concern built on ActiveJob&#x27;s perform callbacks and job-iteration&#x27;s start and complete callbacks.
