You are preparing a new release in Tuleap while part of your project history is still stored in Jira. Your teams need access to previous user stories, tasks, and bugs to continue their work seamlessly in Tuleap.
In this context, migrating the entire Jira project is not always necessary. Importing only the relevant issues can be enough to preserve valuable project information and maintain a consistent history within Tuleap.
Tuleap allows you to import Jira issues on your own and convert them into fully usable artifacts within a tracker. Key information is preserved throughout the process, making it easier to transition to a new work environment without disrupting ongoing projects.
Why Migrate Only Jira Issues?
Not every migration requires recreating an entire Jira project in Tuleap. In many cases, teams simply want to retrieve their project history so they can continue working in Tuleap.
User stories, tasks, and bugs often represent the most valuable part of that history. They preserve past decisions, implemented fixes, project history, and the context behind previous development work.
A targeted issue migration offers several benefits:
- Reduce the time required for the migration
- Minimize configuration efforts
- Simplify post-import verification
- Enable teams to quickly resume their work in Tuleap
This approach is particularly well suited when the Tuleap project is already set up and only the relevant data needs to be imported from Jira.
What Jira data can be imported into Tuleap?
Importing Jira issues is not limited to tickets alone. Depending on the data available in the source project, a significant portion of the context associated with work items can also be preserved.
Teams can notably retain:
- User stories
- Tasks
- Bugs
- Comments
- Change history
- Associated users
- Attachments
- Custom fields (depending on the defined mapping)
The goal is to recreate usable artifacts in Tuleap that remain consistent with the information originally stored in Jira.
Before starting the import, it is recommended to review the quality of the source data. Removing obsolete tickets and unused fields helps streamline the migration process and improves project readability in Tuleap.
