# Epic JIM-80 - Import Jira Sprints

Project: Stream Jira to OpenProject data Migrator
Status: in specification
URL: https://community.openproject.org/work_packages/JIM-80

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q3 |
| Date |  |
| Votes |  |
| List | RM Jira Migrator |
| Target versions |  |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| JIM-44 | Feature | Migrate sprint assignments of work packages including required sprints and sprint attributes | merged |  | 18.0.0 | Stream Jira to OpenProject data Migrator | Immediate |  |
| JIM-32 | Open Point | How does Jira Epic short title work? Where is it stored? | needs clarification |  |  | Stream Jira to OpenProject data Migrator | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| JIM-32 | Open Point | How does Jira Epic short title work? Where is it stored? | needs clarification |  |  |  |

## Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / Jira |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work | · Σ 12d 0h |

## Description

**As** a admin migrating data from Jira  
**I want to** all sprints and related data like backlogs, spring assignments to be available in OpenProject after migration  
**so that** historical data is preserved

**Acceptance criteria**

*   <br>
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
