Content
View differences
Updated by Wieland Lindenthal 7 days ago
# User Problem
## User
* Project Managers
## Problem
* Users need a simple way to migrate basic Jira project data into a new OpenProject instance system without manually recreating structures or copy-pasting issue content.
## Pain
* Current workarounds:
* Use incomplete third-party tools to migrate from Jira DC to OpenProject
* Migrate manually
* This is painful because:
* It is time-consuming and error-prone
* Third-party tools can become outdated quite soon
* Users cannot easily recover mistakes
# Business Case
## Solution
The Jira Migration Tool V1 provides a minimal, reliable way to migrate essential Jira project data into an OpenProject instance.
V1 supports:
* Connecting to a Jira instance via a configured host and credentials
* Fetching the list of available Jira projects
* Letting the user select projects for import
* Fetching and caching the following data:
* Project
* Name
* Description
* Identifier
* Issue
* Subject
* Description
* Issue Status
* Issue Type
* \[Optional\] validation that target configuration is sufficient
* Auto-creation of missing OpenProject-side objects
* Performing the creation of Projects, Work Packages, Statuses, Types from cached data and storing references to all created objects
* These references allow a one-click “Undo import” action
* "Undo import" action
## Out of Scope for the MVC
* Migration of
* Users and Groups
* Issue Comments
* Attachments
* Custom Fields
* Permissions
* Relations
## Differentiation
* "Undo import" provides a way for users to test how migration works.
## Next iterations
* V2:
* Users and groups migration
* V3:
* Project level permissions migration
* V4:
* Issue relationships migration
# Launch and Growth
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* ...
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_
## User
* Project Managers
## Problem
* Users need a simple way to migrate basic Jira project data into a new OpenProject instance
## Pain
* Current workarounds:
* Use incomplete third-party tools to migrate from Jira DC to OpenProject
* Migrate manually
* This is painful because:
* It is time-consuming and error-prone
* Third-party tools can become outdated quite soon
* Users cannot easily recover mistakes
# Business Case
## Solution
The Jira Migration Tool V1 provides a minimal, reliable way to migrate essential Jira project data into an OpenProject instance.
V1 supports:
* Connecting to a Jira instance via a configured host and credentials
* Fetching the list of available Jira projects
* Letting the user select projects for import
* Fetching and caching the following data:
* Project
* Name
* Description
* Identifier
* Issue
* Subject
* Description
* Issue Status
* Issue Type
* \[Optional\] validation that target configuration is sufficient
* Auto-creation of missing OpenProject-side objects
* Performing the creation of Projects, Work Packages, Statuses, Types from cached data and storing references to all created objects
* These references allow a one-click “Undo import” action
* "Undo import" action
## Out of Scope for the MVC
* Migration of
* Users and Groups
* Issue Comments
* Attachments
* Custom Fields
* Permissions
* Relations
## Differentiation
* "Undo import" provides a way for users to test how migration works.
## Next iterations
* V2:
* Users and groups migration
* V3:
* Project level permissions migration
* V4:
* Issue relationships migration
# Launch and Growth
## Measures
_How will you know you solved the problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the solution?_
* ...
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_