Deleting a Project Safely

Deleting a project permanently removes the project and its related project data from AXQA according to the platform's deletion behavior.
Because deletion is irreversible, it should only be performed when the project and its associated testing information are no longer required.

Why it matters

• Prevents accidental loss of important QA information.
• Helps administrators and project owners manage obsolete projects safely.
• Ensures destructive actions are performed intentionally and by authorized users.

When to use it

• When a project was created by mistake.
• When a duplicate or unnecessary project is no longer required.
• When the project and its associated QA data are intentionally being permanently removed.

Core concepts

• Project Owner – The user responsible for the project and authorized to perform supported project-management actions.
• Superuser – An administrative AXQA user with elevated system permissions.
• Permanent Deletion – An irreversible removal operation.
• Related Data – Project-linked information that may be removed as part of the project deletion process.
• Current Project Reference – The user's active project context, which must no longer reference a deleted project.

How it works

1. Open the project you want to delete.
2. Confirm that the correct project is selected.
3. Review whether any project information must be retained.
4. Start the Delete Project action.
5. Confirm the operation.
6. AXQA removes the project and handles supported related project records.
7. References to the deleted project are cleared where required.

How to use it

Step 1: Confirm the project

Before deleting anything, verify:

• Project Name
• Project Owner
• Project Status
• Testing scope
• Builds
• Test Cases
• Test Plans
• APIs
• Execution history

Make sure you are working with the correct project.

Step 2: Review important project information

Determine whether the project contains information that your organization still needs.

This may include:

• Test definitions
• Execution history
• Release evidence
• API definitions
• Builds
• Project reports
• Audit information

Do not delete the project if this information is still required.

Step 3: Confirm your permission

Project deletion is restricted.

The supported deletion flow requires the appropriate project-level authority, such as:

• Project Owner
• Superuser

If you do not have the required permission, AXQA should prevent the deletion action.

Step 4: Delete the project

Start the Delete Project action.

Carefully review the confirmation message before continuing.

Confirm the operation only when you are certain that the project should be permanently removed.

Step 5: Verify the result

After deletion, confirm that:

• The project is no longer available.
• It is no longer your Current Project.
• Project-specific links or workflows are no longer being used.
• Your team knows the project has been intentionally removed when applicable.

Best practices

• Use deletion only when permanent removal is actually required.
• Double-check the Project Name before confirming.
• Review project history and evidence before deleting.
• Make sure required information has been retained according to your organization's policies.
• Restrict project ownership and Superuser access to appropriate users.
• Prefer keeping valid historical projects when their QA evidence is still useful.

Common mistakes

❌ Deleting a project when you only wanted to stop working on it temporarily.
✔ Use Pause to remove the Current Project context without deleting the project.

❌ Deleting a project because testing is finished.
✔ Use the appropriate Project Status when the project should remain available as historical QA evidence.

❌ Assuming deletion can always be reversed.
✔ Treat Project Deletion as a permanent operation.

❌ Deleting a project without reviewing its execution history.
✔ Confirm that important testing evidence is no longer required before deletion.

Security & permissions

• Project deletion is a restricted destructive operation.
• The current deletion flow is limited to the Project Owner or Superuser.
• Deletion does not provide a replacement for normal Project Lifecycle management.
• Related project records may be removed as part of the deletion process.
• Current Project references are cleared where required when the associated project is deleted.
• Never perform deletion using a shared administrative account.

Related documentation

• Project Overview
• Current Project: Activate, Switch & Pause
• Managing Project Settings
• Project Lifecycle
• Project Visibility & Access Control
• Project Membership & Access Roles
• Cloning a Project