You are not logged in. Click here to log in.

codebeamer Application Lifecycle Management (ALM)

Scheduled Maintenance today at 12:00 CET


Search In Project

Search inClear

Tags:  not added yet

Risk Management trace direction change

In this release, the link directions between Causing Requirements, Risks and Mitigation Requirements have been reversed as per the diagram below. We believe that the new direction reflects the causality of items better.



Migration

Along with this change, the deployment of this release is also going to apply the following changes to the database:

  • In Requirement type trackers:
    • "Risk" field has been renamed to "Mitigates" (choiceList[1]) and has other meaning than before: from now, the Mitigation Requirements are handled via the "Mitigates" field of a Requirement which points to Risk item(s) (we define which Risk(s) mitigates the current Requirement). Removed the default "Reverse direction" from the field (but still remained Suspected by default).
      The references in this fields are moved to the Risk tracker "Caused by" field in the other direction.
  • In User Story and Epics trackers:
    • "Risk" (choiceList[0] in both trackers) field has been removed: the issues which cause Risks are handled in Risk tracker.
      The references in this fields are moved to the Risk tracker "Caused by" field in the other direction, and then the field should be deleted.
  • In Risk type trackers:
    • "Mitigation Requirements" field has been renamed to "Caused by" (choiceList[2]) and has other meaning than before: from now, the Risks of the Requirements are handled via this field which points to Requirement/User Story/Epic type trackers (we defined that the current Risk is caused by an other issue).
      The references in this fields should be moved to the Requirement tracker "Mitigates" field in the other direction.

Skipping the data migration

You may want to skip the execution of the migration (i.e. if you have already changed the direction of the links manually). This can be done by creating the following environment variable:

cbSkipRiskMigration102

The value of the env variable does not matter, codeBeamer only checks for its existence.


Manually triggering the data migration

If you need to manually trigger the data migration for any reason (i.e. if you are upgrading from a SNAPSHOT version that did not yet contain the migration):

  1. Have all the projects on the environment of which Test Runs you would like to get migrated
  2. Execute the following SQL query:
    DELETE FROM upgrade_statements WHERE statement_id LIKE '10.2.0-Risk-Migration'
    UPDATE version SET major='10.1'
  3. Restart your codeBeamer environment
  4. Check the logs for issues