In addition to the one-time import of epics from Jira, you may also set up recurring imports.
Once you set up the recurring import query, it runs daily. You may also manually start an import by clicking the "Run the recurring import now" button.
You may set up, turn on and off, and modify recurring imports on the Integration >>One time and Recurring Import setting.
A typical roadmapping workflow starts in Dragonboat by defining objects, prioritizing ideas, defining timeframe, and pushing to Jira as EPIC at the end of the planning stage (the top-down approach).
There are scenarios where some of your team may create EPIC directly in Jira (the bottom-up approach). The recurring/automated import feature pulls these EPICs into Dragonboat daily (or on-demand) to ensure the roadmaps are in sync.
A sample recurring import JQL looks like this:
Project in (X,Y,Z) and issuetype = epic and created >-2d
Because the recurring import runs often, adding a time parameter will greatly help with the performance of your Jira. Epics already in Dragonboat will be skipped from the import, no be added again.
Note: You can also use Basic Search rather than just the Advance Search JQL for your epics, the URL that shows once your search terms are complete is what you'll use in Dragonboat.
During recurring import, you may map fields between your Jira EPIC fields and Dragonboat fields.
Questions? Use the Help widget on the bottom right of your screen to search the knowledge base, reach to our support team. Or join our Slack community.