| Tip | ||
|---|---|---|
| ||
This page is provided for help. It is not normally part of the installation. When to use this page? This is a help document in case you are renaming the key of a space, or when attempting to export-then-import a space. |
If you rename spaces, then Requirement Yogi doesn't automatically track the change. You will have to perform a lot of operations manually.
...
| title | Alternative |
|---|
The other way of doing it is to let Requirement Yogi reindex:
- Change the space key,
- Launch Requirement Yogi's reindex,
It will:
...
Exporting a space in XML
When exporting a space, we don't include the requirements in the export. Therefore, the following information will be lost:
- Baselines will be lost,
- Links from other spaces will be lost,
- Links from Jira will be lost. They will still appear on the Jira side, but will reach a 404 page in Confluence. They won't appear on the new requirements in Confluence.
After you reimport, please use Requirement Yogi's reindexation in the space administration.
Renaming a space
If you rename a space, our records in the database still point to the older space. Therefore, requirements will appear as non-existing in the new space. You have two choices:
- If you don't have baselines, links from Jira or from other spaces, then you can use the same method as above: Reindexing the space, which will only create the current versions of requirements.
- Otherwise, you will have to perform a lot of operations manually, see below.
Places where the space key is mentioned
...