Project Nuke

Project Nuke is a feature that allows users to permanently delete a selected project from their instance.
The deletion process includes:
- The project itself (not moved to trash or archive but actually deleted).
- All issues related to the project.
- All non-shared schemes associated with the project, such as permission schemes, notification schemes, and issue security schemes.
Shared schemes that are used by multiple projects are not deleted to prevent unintended impact on other projects.
The time required for deletion varies depending on the project size and instance complexity, ranging from a few seconds to potentially up to half an hour.

Backup: It is highly recommended to perform a backup of the data before using Project Nuke to prevent any irreversible data loss.
Testing: Users should test the deletion process in a non-production environment (e.g., dev, staging, sandbox) before applying it to production.
Data Refresh: Before initiating deletion, refreshing the data (projects and schemes) ensures the tool has the latest state of the instance.
Post-Deletion Refresh: After the deletion process, refreshing reports or data after approximately 30 minutes provides an accurate reflection of the updated instance status.

The presenter showcases the feature by selecting projects from the instance.
Two examples are highlighted:
1. Las Vegas project:
  - Identified three non-shared schemes eligible for deletion: permission scheme, notification scheme, and issue security scheme.
  - The project is team-managed, limiting deletion options.
2. Miami project:
  - Five schemes detected: three non-shared (deletable), two protected/shared (not deletable), and one default scheme.
  - Demonstrates the tool’s respect for shared schemes, preventing their deletion.
The user interface displays:
- Instance URL to confirm environment (production, dev, staging, sandbox).
- Number of tickets/issues associated with the project.
- Exact list of schemes and components scheduled for deletion.
The process proceeds with a single button click, triggering asynchronous backend API calls.
Progress is displayed during cleanup, with a status report upon completion.
Users can export the deletion summary and metrics as a CSV file for record-keeping or auditing.

Project Nuke offers a simple yet powerful one-click solution to completely remove a project and all its related non-shared components, which is highly valuable for administrators managing large instances.
The tool is designed with safety in mind, clearly distinguishing between deletable and protected/shared schemes to avoid accidental data loss.
The inclusion of backup and testing recommendations reinforces the importance of cautious use of such a destructive feature.
The ability to export deletion metrics provides transparency and accountability in administrative actions.
Refreshing data before and after deletion ensures consistent and up-to-date system states, minimizing errors or stale data issues.
The varying process time depending on project size highlights the need for patience and planning when performing large-scale deletions.

The video does not specify the supported platforms or versions for Project Nuke.
There is no information on recovery options post-deletion, reinforcing the necessity for backups.
The feature’s applicability to different project types beyond team-managed and standard projects is not specified.
The video does not elaborate on the user permissions required to execute the Project Nuke feature.

Always backup your data before using Project Nuke.
Use the feature first in a test or staging environment.
Review the project and scheme list carefully during the confirmation step.
Monitor the deletion progress and wait for completion before making further changes.
Export the deletion report for documentation and auditing purposes.
Refresh your data and reports after the deletion to ensure accuracy.