Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

It may happen that pages are not migrated, for several reasons:

  • Requirement Yogi can’t recognize the format,

  • Confluence rejects the modification, for example if Confluence rate-limited the app because it was performing too many modifications,

  • Or if the users have restrictions on pages, which is very frequent. If users have put restrictions on the permissions of pages, then the app’s user can’t edit those pages.

No worries, pages can be migrated at any time in the future!

  • First, see below how to create a saved transformation for one page,

  • Then search for non-migrated pages and transform them in bulk.

The upside of manual transformations is, they are performed with the current user’s permissions.

Creating a transformation for a “Migration” step

  • Go to a page that needs to be migrated,

  • Click the “…” menu at the top-right, then click “Requirement Yogi”,

  • In the dialog, select “Add rule” → “Migrate server requirement macros to cloud”,

  • Before launching the transformation, add a name, so that it is saved.

Applying the transformation in bulk

  • Go to a space that needs to be migrated,

  • In the sidebar, click Requirements → Pages tab,

  • Enter the search query below, and tick the “Use CQL” checkbox:

    # Don't forget to tick "Use CQL"
type=page AND macro=requirement AND ryc_isMigrated !=true

  • If pages have been indexed by Confluence, they will be listed,

  • Select all of them (don’t forget to navigate to the next pages and select those pages as well),

  • Note: The video shows a blank query while selecting pages, this is not what you should do. We had to record the video this way because we didn’t have any page that needed to be migrated,

  • At the bottom-right, in “Select a transformation”, choose your transformation, then click the button Transform.

Your pages will be transformed in bulk, with your permissions. You can perform this step at any point in the future, if you notice that a page wasn’t migrated. Since this search is performed by space, you’ll need to repeat this operation in any space that requires it.

Demonstration

Note: While using the “Pages” tab and the search, the search query is blank (because we couldn’t record the video with pages that needed a migration). Don’t do like us, don’t forget to enter the search query and only select pages which need a migration.

How to migrate pages in bulk.mov

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).

  • No labels