- You are here:
- GitLab Direction
- Product Vision - Plan
- Category Direction - Jira Importer
Last reviewed: 2020-03-04
🚥 Jira Importer
Introduction and how you can help
👋 This is the category direction for Jira Importer in GitLab; which is part of the Plan stage's Project Management group. Please reach out to the group's Product Manager, Gabe Weaver (E-mail), if you'd like to provide feedback or ask any questions related to this product category.
This category direction is a work in progress and everyone can contribute:
- Please comment and contribute in the linked issues and epic on this page. Sharing your feedback directly on GitLab.com is the best way to contribute to our strategy and vision.
- Please share feedback directly via email, Twitter, or on a video call.
Overview
Jira is one of the most common project and portfolio managmenet tools with roughly 34% market share. Many GitLab customers that purchase GitLab for source code management
or CI/CD functionality continue to use Jira due to:
- The lack of an easy migration path from Jira to GitLab.
- Missing capabilities within GitLab that are necessary for teams to plan and manage their work effectively.
We are focusing on providing a great Jira importing experience in lock step with improving GitLab's planning capabilities. It is our goal to make it effortless for our customers to start realizing the increased value and efficiencies that are unlocked when project and product management is colocated within the same application as the rest of the DevOps lifecycle.
Where we are Headed
What's Next & Why
These are the epics and issues that we will be working on over the next few releases:
- Leverage our existing Jira Service Integration to deliver an MVC Jira Project > GitLab Project importing experience.
- Outcome: Project Admins/Owners can import basic issue data (Title, Description) from a Jira to Gitlab
- Extend the importer to support additional data mapping as outlined in the follow-up iterations
- Outcome: Jira issues can be imported to GitLab without losing contextual information such as comments and their original authors, issue dependencies and relationships, and epics. We provide verification that 100% of the targeted issues were successfully imported into GitLab.
What is Not Planned Right Now
- Importing complex workflows, triggers, and automations from Jira to GitLab. As GitLab's capabilities mature, we will revisit whether or not this would provide additional value for teams looking to move from Jira to GitLab.
- Importing Confluence wikis to GitLab wikis. While we intend on supporting this at some point in the future, we are currently focused on creating a Jira Software importer that helps teams transition their issue management to GitLab.
Maturity Plan
This category is currently at the 😊Planned maturity level, and our next maturity target is 😁Minimal by 2020-04-22.
We are tracking our progress against this target via this epic.
User success metrics
- 100% of targeted issues are imported successfully from Jira into GitLab.
- Count of total issues imported.
- Count of projects that imported issues from Jira to GitLab.
- Count of instances using the Jira issue importer.
Top Customer Success/Sales issue(s)
Top user issue(s)
Top internal customer issue(s)
- Not applicable as we use GitLab for issue management.
Top Strategy Item(s)
This is a non-marketing category which was created as a specific strategy to help drive our 1 year plan of importing from Jira without losting required data. While the importer itself is an important component of this, we also need to maintain focus on adding capabilities to GitLab that enable us to win successfully against competitors like Jira.
