Dragonboat is a complete portfolio platform dynamically connects strategy and execution. Product managers and tech leaders use Dragonboat to define goals and strategies, prioritize features, visualize roadmaps, and allocate resources (if needed). Once features are ready for execution, they will be pushed from Dragonboat to Jira for execution.
Dragonboat access is not limited by Jira user access. You can create customized beautiful roadmap dashboards for your stakeholders (non-Jira users) via Read-Only access.
If you currently use Jira Premium (previously known as Jira Portfolio, Advanced Jira), you may either use Dragonboat as a portfolio tool integrated with Jira Software, or use both in parallel via importing/ syncing your Epics along with their Initiatives (parent link) to Dragonboat. You'd need an Enterprise plan to use this feature.
To link an existing Jira Initiative issue with a Dragonboat Initiative, you may enter the Jira key for the initiative to the Link Jira field in the Integration section of the Edit screen.
You may also enter the Jira project key and click the Create Jira to create an Initiative issue in Jira.
To start, import the relevant Jira EPICs of your current Portfolio plans to Dragonboat via a one time import (JQL). If you'd like to run the two systems in parallel for a while, you may use the recurring import feature.
One time import from Jira Portfolio to Dragonboat:
The background (and a limitation due to the set up between Jira Portfolio and Jira Software):
- Jira Portfolio and Jira Software are two separate systems. Initiative (in Jira Portfolio) is connected to EPICs (in Jira Software) via "parent link".
- Jira Software does not have an Initiative name. It only has a "parent link."
Due to the above, the import takes two steps:
1. Import your EPICs via JQL (you may find import options on the Idea List, Idea Board, and Settings >> Integration page). Your JQL may look like this:
issuetype = epic and statusCategory != done
Or if you'd like to import only the selected initiatives, your JQL may look like this:
parentlink in (X, Y, Z) and issuetype = epic
issuetype= epic and project in (A, B, C) and parentlink is not empty
During Jira import, on the data mapping screen, select Dragonboat Master EPIC and link to Jira Parent Link (you may rename Master EPIC to another name later).
The field mapping of Initiative and Idea is shared.
Recurring Import from Jira to Dragonboat
In case you want a cooling-off period / gradual transition, Dragonboat enables parallel usage of both Portfolio and Dragonboat because both systems sit "on top of" Jira.
During this phase, you may set up Recurring import for a set of Initiatives.
1. Go to Setting >> Integration page and click Import EPICs panel and turn on recurring Import
2. Go to Jira, use JQL to search within a set of existing initiatives, similar to this
"Parent Link" in (KEY-1252, KEY-1251) and created > -2d
issuetype= epic and project in (A, B, C) and "Parent Link" is not EMPTY and created > -2d
Copy and paste the page URL to the import screen...Similar to the One Time Import (in step 1). The EPICs in these Initiatives will be pull in from Jira and mapped to their parent links in Dragonboat on a daily basis (or on-demand on this page)
Note: Once an Idea (EPIC) is added to Dragonboat at the time of import, changing its Roadmap or Master EPIC (initiative) within Dragonboat will not automatically update Jira parent link.
Question or feedback? Please use the Chat or Help widget on your screen to reach us.
Join our Slack Community