NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Issue Summary
When a project is deleted in JIRA, various configurations as well as users remain in it hence achieving a full clean delete is difficult.
For example, if I restore a backup but require just one project, if I delete all the other projects, settings such as permission scheme, configuration scheme, Workflows and users are still left in the system.
The feature we would like implemented would be able to delete all of these when the project is deleted.
Suggestion:
As most schemes can be shared, a notification should be shown when user attempts to delete a project that has such a shared scheme and the user would be allowed to confirm this.
If they confirm it, revert all such settings back to the default schemes for them.
- is related to
-
JRACLOUD-79026 Provide ability to identify and bulk delete unused schemes
- Closed
-
JRASERVER-45256 Allow full project delete.
- Closed
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management