Created By  inflectra.adam Tuesday, January 16, 2018

Some of our customers wanted to know that we delete the data in the SpiraTest, SpiraPlan, and SpiraTeam tables when we delete a project. This article outlines the approximate order in Spira v5.3.0.2.

  • Deletes all the data mappings (TST_DATA_SYNC_SYSTEM and related tables)
  • Deletes all the attachments (TST_ATTACHMENTS and related tables)
  • Deletes all the incidents (TST_INCIDENT and related tables)
  • Deletes cross-project associations (TST_PROJECT_ASSOCIATION and related tables)
  • Deletes all the test runs (TST_TEST_RUN and related tables)
  • Deletes all the test sets (TST_TEST_SET and related tables)
  • Deletes all the test cases (TST_TEST_CASE and related tables)
  • Deletes all the requirements (TST_REQUIREMENT and related tables)
  • Deletes all the releases (TST_RELEASE and related tables)
  • Deletes all the test automation information (TST_AUTOMATION_HOST and related tables)
  • Deletes all the incident types (TST_INCIDENT_TYPE)
  • Deletes all the incident workflows (TST_WORKFLOW and related tables)
  • Deletes all the requirement workflows (TST_REQUIREMENT_WORKFLOW and related tables)
  • Deletes all the task kworkflows (TST_TASK_WORKFLOW and related tables)
  • Deletes all the release workflows (TST_RELEASE_WORKFLOW and related tables)
  • Deletes all the test case workflows (TST_TEST_CASE_WORKFLOW and related tables)
  • Deletes all the project custom properties (TST_CUSTOM_PROPERTY and related tables)
  • Deletes all the saved project reports (TST_REPORT_SAVED and related tables)
  • Deletes all the project history records (TST_HISTORY_CHANGESET and related tables)
  • Deletes the project itself (TST_PROJECT and related tables)
Article Info
  • Last Updated: 1/16/2018
  • Article ID: KB315
  • Views: 593