# Bug JIM-262 - Wrong advice from Jira migrator in case of project identifier conflict

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

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module | Integrations / Jira |
| Target versions |  |
| Observed in versions | 17.9.2 |
| 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 |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

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

## Costs

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

## Description

### Steps to reproduce

1.  Import a project having a Jira project key already used as a project identifier in OpenProject (you can import the same project twice to trigger it)
    
    1.  The second import will fail at the create projects step.
        
    2.  The Jira importer says: "You are trying to import a project with an already used identifier: XXX. Please update the project identifier in Jira then click on Retry."
        
2.  Do as the Jira importer says and change Jira project key ([doc](https://confluence.atlassian.com/adminjiraserver/editing-a-project-key-938847080.html)):
    
    1.  In the upper-right corner of the screen, select **Administration** > **Projects**.
        
    2.  Select the project that you'd like to change.
        
    3.  Select **Edit** in the **Actions** column of the project you want to change.
        
    4.  Edit the project key, and click **Save details**. 
        
3.  Once Jira project key is changed, click "Retry"
    

### What is the buggy behavior?

*   The same error is displayed
    

### What is the expected behavior?

1.  One tiny thing first: Message says "update the project identifier in Jira". It's a "project key" in Jira terminology. The message should be updated.
    

It seems to happen because the migrator keeps a cache of project information to be imported

1.  The migrator should get the new identifier and continue
    

OR

1.  The migrator could fail earlier before caching project information
    

OR

1.  The error message could be changed to advise to change the Jira project Key and then click revert and try again.
    
    1.  Would be bad from a user stand point as they would have to do it all over again.
        

### **S**creenshots and other files

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925948/content">

### Environment information

**OpenProject installation type**

*   [x] Cloud edition
*   [ ] On-Premise
*   [ ] Packaged installation
*   [ ] Docker All-in-one container
*   [ ] Docker-compose installation
*   [ ] Other (please specify)

**OpenProject version**

17.9.2

**Browser**

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

**Operating System**

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

**Language**

*   [x] English
*   [ ] German
*   [ ] Other: