...

We know the migration tool isn’t one of the most stable. Of course it doesn’t excuse it, but we’ve spent a tremendous amount of work from our side, for little of our satisfaction. We present our apology to customers who will be affected by this outcome.

What about Jira?

It is not possible to perform the migration manually in bulk in Jira.

• Either you extract data manually from the traceability matrix, and create issues in Jira manually,

• Or you need to upgrade to Requirement Yogi 3.7.2 or above (version is subject to change if we perform new improvements).

How to manually extract Jira data from Confluence?

You only need to extract requirement-issue relationships. You can do this with a traceability matrix.

• Open a traceability matrix in any space, with administrator rights,

• Use the search query jira is not null to only display requirements with Jira links,

• Add a new column: Column heading → cog menu → Jira → All issues,

• Important: Click “Cross-space search” at the top-right.

• Export the matrix in Excel if you need to.

Then go to each Jira issue on the Cloud, and create the link manually. Note that there is some keyboard navigation for the Jira panel (Try the tab-arrow-space-enter-esc keys).