# Feature JIM-164 - Improve error reporting by providing more context

Project: Stream Jira to OpenProject data Migrator
Status: closed
URL: https://community.openproject.org/work_packages/JIM-164

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List | RM Jira Migrator |
| Roadmap | 2026 Q4 |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| JIM-228 | Code maintenance | Unify usage of Rails logger and OpenProject logger | closed | Pavel Balashou | 17.9.0 |  |  |
| JIM-227 | Task | Do a first implementation using tags | closed | Kristine Jetzke | 17.9.0 |  |  |
| JIM-229 | Code maintenance | Add tags to all log messages and unify log levels | closed |  | 18.0.0 |  |  |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Pavel Balashou |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

It is very likely that the importer will stumble upon unknown errors during import. Mainly because there will be edge cases in Jira that we did not consider before.

In order to ease debugging - either for OpenProject devs but also for the users directly - we should provide more context on the data that caused the error. Both in the backtrace / log messages and the UI.

*   Identifiers to use
    
    *   Each import run has a UUID
        
    *   Use structured logging
        

```text
{
    "runID": UUID,
    "goodJobData": text,
    "jiraProjectKey": text,
    "jiraIssueKey": text,
    "jiraObjectType": project|attachment|issue|user|customField|status,
    "jiraObjectIdOrName": text,
    "message": text
}
```

*   Levels
    
    *   DEBUG: Every single object
        
    *   INFO: Status updates e.g. project X import started, project X import finished, summary
        
    *   WARN:
        
        *   if data is not found, something is skipped etc. but import continues
            
        *   Data being changed e.g. user name sanitized, status de-deduplication
            
    *   ERROR: if whatever happens causes the import to fail
        
*   Where should we store the log (file, database?)
    
    *   General log file
