| Tip | ||
|---|---|---|
| ||
As highlighted in Release 3.0 – Estimates, we had to migrate the data for Requirement Yogi 3.0. In theory, you shouldn't need to refer to this page. In practice, if there is any issue, we will mention it here. |
| Table of Contents |
|---|
How long should we wait?
In our experiments, the generally observed speed is 1000 requirements migrated every time the background task executes. We execute the task every minute, for 30s only.
...
| Old table | New table | Observations |
|---|---|---|
AO_32F7CE_AOREQUIREMENT | AO_32F7CE_DBREQUIREMENT | Requirements. Columns have been cleaned up |
| AO_32F7CE_AOREQUIREMENT_LINK | AO_32F7CE_DBLINK | Links to requirements. Types are cleaned up. |
| AO_32F7CE_AODEPENDENCY | AO_32F7CE_DBDEPENDENCY | Dependencies. Much better cross-baseline management |
| AO_32F7CE_AOPROPERTY | AO_32F7CE_DBPROPERTY AO_32F7CE_DBPROPERTYNAME | Properties. Added the implementation of the External Properties |
AO_32F7CE_AOINTEGRATION | AO_32F7CE_DBAPPLINK | The queue and the descriptor. |
| AO_32F7CE_AOBASELINE | AO_32F7CE_DBBASELINE | The baseline descriptors. |
| AO_32F7CE_AOISSUE_TEMPLATE | AO_32F7CE_DBISSUE_TEMPLATE | Templates for the Jira Bulk Issue Creation. |
| AO_32F7CE_AOTRACEABILITYMATRIX | AO_32F7CE_DBTRACEABILITYMATRIX | Traceability matrixes. |
| AO_32F7CE_AOSETTINGS | AO_32F7CE_DBSETTINGS | Settings. |
| In Jira | ||
AO_42D05A_REMOTEREQUIREMENT
| AO_42D05A_DBREMOTEREQUIREMENT | The requirements and their associations with Jira issues. |
| AO_42D05A_RYAUDITTRAIL | AO_42D05A_DBAUDITTRAIL | The history of requirements (large table). |
| AO_42D05A_INTEGRATION AO_42D05A_AOQUEUE_MESSAGE | AO_42D05A_DBINTEGRATION | The queue and the descriptor. |
| AO_42D05A_ISSUE_OPERATION_JOB | AO_42D05A_DBOPERATIONJOB | The Jira Bulk Issue Creation jobs, while they are executing. |
| AO_42D05A_TASK | We keep the old table. | Status of the background migration tasks. |
...
FAQ
There are error messages, what should I do?
...