# Bug JIM-184 - Jira import fails when historical issues reference deleted Jira users

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 17.9.0 |
| Observed in versions |  |
| Sprint |  |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

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

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Configure a Jira import in OpenProject.
    
2.  Select a Jira project containing historical comments authored by users that no longer exist in Jira. (Previous existing user who write a comment in the past and then have been deleted from Jira User Management)
    
3.  Start the import.
    
4.  During the user collection phase, Jira returns `404` for the historical user key.
    
5.  OpenProject skips the user during the collection phase.
    
6.  During the issue and comment import phase, the import fails with:
    

```text
Import::JiraUser with jira_user_key [REDACTED_USER_KEY] not found!
```

### What is the buggy behavior?

*   OpenProject ignores the missing Jira user during the user collection phase.
    
*   The same missing user later causes the complete import to abort during the issue/comment import phase.
    
*   The import cannot be completed.
    

### What is the expected behavior?

The import should continue when a historical Jira user can no longer be resolved.

Possible fallback behaviors include:

1.  Assign comments and attachments to the OpenProject system user.
    
2.  Leave missing assignees empty.
    
3.  Create an “unknown Jira user” placeholder.
    
4.  Try to resolve the user by username when the lookup by Jira key returns `404`.
    

The missing user should generate a warning in the logs, but should not abort the complete import.

### Important note

Recreating a Jira user with the same visible username and re-indexing Jira did not resolve the issue. The Jira API continued to return `404` for the original user key.

### Logs

```text
Error fetching user data for user key [REDACTED_USER_KEY]:
Jira API returned error status 404
```

Later, during the issue import:

```text
Import::JiraUser with jira_user_key [REDACTED_USER_KEY] not found!
```

### Screenshots and other files

_None_

### Environment information

**OpenProject installation type**

*   Docker-compose installation
    

**OpenProject version**

_v17.7.2_

**Browser**

*   [ ] Chrome
*   [x] Firefox
*   [ ] Safari
*   [ ] Mobile Safari
*   [ ] Other (please specify)

**Operating System**

*   [x] Windows
*   [ ] Mac OS X
*   [ ] Mobile iOS
*   [ ] Mobile Android
*   [ ] Linux (please specify distro)
*   [ ] Chrome OS
*   [ ] Other (please specify)

**Language**

_\- OpenProject: English_  
_\- Jira: English_
