...
- Our requirement is that the following tables are correct:
- AO_32F7CE_DBBASELINE
- AO_32F7CE_DBREQUIREMENT - Simple import
- AO_32F7CE_DBPROPERTY- Simple import (with foreign key to DBREQUIREMENT),
- AO_32F7CE_DBLINK - Don't forget to change the Page IDs and the Jira Applink ID.
- AO_32F7CE_DBDEPENDENCY - Import (with foreign key to DBREQUIREMENT) + references to DBLink.
- Don't forget AO_32F7CE_DBBASELINE, AO_32F7CE_DBTRACEABILITYMATRIX, AO_32F7CE_DBISSUE_TEMPLATE.
- Our other requirement is that tables in Jira correctly match the tables of Confluence:
- AO_42D05A_DBREMOTEREQUIREMENT
- AO_42D05A_DBISSUELINK
- AO_42D05A_DBAUDITTRAIL
- So, the process would be:
- Import a space to the new Confluence,
- Find a way to map old page IDs to new page IDs,
- Import all RY tables, keeping foreign keys,
- Change Applink IDs in DBLink,
- Change Page IDs in DBLink,
- Jira: Before exporting, ensure issue numbers match issue ids, in DBIssueLink,
- Jira: Import all RY tables,
- Jira: After importing, update issue ids to issue numbers in DBIssueLink,
- Jira: Update the Applink IDs in DBRemoteRequirement.
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:
...