Deleting a project should delete the schemes if they are unused

Problem Definition

Currently, as stated in Delete a Project:

Deleting a project will only delete the issues, versions, and components associated with the project. It won't delete any of the associated schemes, workflows or issues types, or any content that could be shared with another project.

This means after deleting a bulk of projects, Administrator has to go through all the Schemes in JIRA to make sure all the unused Schemes has been removed from the instance.

Suggested Solution

The only reason why the Schemes are being deleted during Project Deletion is that the Schemes could be used by another Project.

It would be better if we have a verification during Project Deletion to check if the Schemes are being used by any other Projects.

• If yes, then just continue the process as it is.
• If no, then prompt another dialog to the Administrator to mentioned that these are the Schemes that will be the orphan Schemes after Project Deletion and would the Administrator wants to delete the Schemes during the Project Deletion.

It also will be good if JRACLOUD-64878 get implemented, which will reduce an Administrator job to clean JIRA data. Or allow Administrator to bulk delete schemes as per JRACLOUD-41977.