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, more specifically its space keyor 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.
...
Note | ||
---|---|---|
| ||
The other way of doing it is to let Requirement Yogi reindex:
It will:
|
Places where the space key is mentioned
- In search queries, for example in the Traceability Matrix,
- In the "requirement" macro, if it represents a link to a requirement in another space,
- In various requirement tables,
- In Jira issues.
How to modify the XML of pages
There is no "clean" way of doing that, you will have to issue SQL instructions.
...
To perform an accurate migration, you will have to write an XML parser.
Tables in the Confluence database
You will have to modify the following tables in the database, which contain the spaceKey parameter:
...
Note that if you also change the Jira application, you will also have to change AO_32F7CE_AOINTEGRATION to update the Applink ID. This is also documented, in Admin - Changing Applinks.
Tables in the Jira database
- AO_42D05A_REMOTE_REQUIREMENT, change the spaceKey.
- AO_42D05A_AOQUEUE_MESSAGE (starting from version 2.6, not published at the time of writing), change the spaceKey inside of the JSON column. More simply, send all messages from the RY administration in Jira before starting.
...
- AO_42D05A_REMOTE_REQUIREMENT, change the spaceKey.
- The plugin settings table, check all keys starting with "com.playsql.requirementyogijira."
Summary
As a summary, there are 5 types of places where you will have to perform modifications:
...