This page lists, for each level of a Data reset, what happens to each kind of data of the project or environment you chose.
This page is generated from the product code; do not edit by hand.
| Level (as shown) |
Scope |
Who may choose it |
| Test history |
The whole project, one environment or one workload |
Project Admin, System Admin |
| History and release records |
The whole project |
System Admin |
| Everything (remove the project) |
The whole project |
System Admin |
| Everything (remove the environment) |
One environment |
System Admin |
Removed: the data goes, after the grace period. Kept: the data stays as it is. Kept, unlinked: the data stays, but no longer points to the removed project or environment.
| Data |
Test history |
History and release records |
Everything (remove the project) |
Everything (remove the environment) |
| Runs, test results, attempts and files (reports, traces, videos, screenshots); test account leases of those runs |
Removed |
Removed |
Removed |
Removed |
| Error signatures and failure groups, with their history |
Removed |
Removed |
Removed |
Removed |
| AI diagnoses and their votes |
Removed |
Removed |
Removed |
Removed |
| AI summaries |
Removed |
Removed |
Removed |
Removed |
| Investigations, with their evidence and events |
Removed |
Removed |
Removed |
Removed |
| Environment health samples, daily health and incidents |
Removed |
Removed |
Removed |
Removed |
| Daily figures and the state of each test (rebuilt from the runs that remain) |
Removed |
Removed |
Removed |
Removed |
| Report snapshots and their share links |
Removed |
Removed |
Removed |
Kept |
| Gate evaluations and readiness assessments |
Removed |
Removed |
Removed |
Kept |
| Test debt history |
Removed |
Removed |
Removed |
Kept |
| Notifications |
Removed |
Removed |
Kept, unlinked |
Removed |
| Data |
Test history |
History and release records |
Everything (remove the project) |
Everything (remove the environment) |
| Releases, with their decisions, approvers, approvals, scope changes, checklist items and evidence |
Kept |
Removed |
Removed |
Kept |
| The environments of each release |
Kept |
Removed |
Removed |
Removed |
| Regression cycles and their snapshots |
Kept |
Removed |
Removed |
Removed |
| Gate policies and their rules |
Kept |
Removed |
Removed |
Kept |
| Requirements and their links to releases |
Kept |
Removed |
Removed |
Kept |
| Risks |
Kept |
Removed |
Removed |
Removed |
| Report schedules |
Kept |
Removed |
Removed |
Kept |
| Quarantine proposals |
Kept |
Removed |
Removed |
Kept, unlinked |
| Jira issue links |
Kept |
Removed |
Removed |
Kept |
| Data |
Test history |
History and release records |
Everything (remove the project) |
Everything (remove the environment) |
| Environments |
Kept |
Kept |
Removed |
Removed |
| Workloads |
Kept |
Kept |
Removed |
Kept |
| Workload revisions |
Kept |
Kept |
Removed |
Kept |
| Which workloads run on which environments |
Kept |
Kept |
Removed |
Removed |
| Variables and profile overrides |
Kept |
Kept |
Removed |
Removed |
| Secrets |
Kept |
Kept |
Removed |
Removed |
| Run grants |
Kept |
Kept |
Removed |
Removed |
| Environment locks |
Kept |
Kept |
Removed |
Removed |
| The current health of each environment |
Kept |
Kept |
Removed |
Removed |
| Test accounts |
Kept |
Kept |
Removed |
Removed |
| Test accounts that workloads need |
Kept |
Kept |
Removed |
Removed |
| The test catalog, with owners and triage labels |
Kept |
Kept |
Removed |
Kept |
| Quarantine entries |
Kept |
Kept |
Removed |
Kept |
| Release checklist templates |
Kept |
Kept |
Removed |
Kept |
| Quality settings of the project |
Kept |
Kept |
Removed |
Kept |
| Integrations (Jira, Teams) and notification rules |
Kept |
Kept |
Removed |
Kept |
| Saved views |
Kept |
Kept |
Removed |
Kept |
| Assistant conversations |
Kept |
Kept |
Removed |
Kept |
| Data |
Test history |
History and release records |
Everything (remove the project) |
Everything (remove the environment) |
| Project roles of teams; the project’s own teams and their members |
Kept |
Kept |
Removed |
Kept |
| Personal settings that name the project |
Kept |
Kept |
Kept, unlinked |
Kept |
| Data |
Test history |
History and release records |
Everything (remove the project) |
Everything (remove the environment) |
| The reset itself (kept in Past resets) |
Kept |
Kept |
Kept, unlinked |
Kept, unlinked |
| AI usage records |
Kept |
Kept |
Kept, unlinked |
Kept |
| Delivery log of integrations |
Kept |
Kept |
Kept, unlinked |
Kept |
| Records of purged runs |
Kept |
Kept |
Kept |
Kept |
- A reset waits 7 days before it removes anything. Until then you can cancel it.
- The export of a removal level is kept for 90 days after the removal is done.
- Test history of one environment or one workload removes only the runs of that scope. Report snapshots, share links, gate evaluations, readiness assessments and the test debt history go only with a whole-project reset; readiness assessments that a release decision rests on stay. Failure groups go only when no result is left in them.
- History and release records keeps only the active quarantine entries; ended ones go.
- Everything (remove the environment) is refused while a decided release uses the environment.
- People’s accounts are never removed. Only the teams that the project created for itself go with it; teams made by hand stay.
- How to reset: Reset test data. How to remove a project or an environment: Remove a project or an environment.