Hi there, Is there a way of moving a project to trash that also removes it's associated things get deleted: * Issue Type schemes * Issue Types (unused) * Screen Schemes * Screens * Workflow Schemes * Workflows * Field Configuration Schemes * Custom Fields * Issue Security Schemes * Notification Schemes * Permission Schemes I've been going in and deleting these manually and frankly it's tedious... At the very least give me a multiselect tool so that I can bulk delete these unused items. I hope that a better way of doing this exists. Please let me know.

I'm still a fairly new admin so I found myself stumbling across project components I thought would have already been removed. I spent around 3 hours removing all traces of deleted projects the other night. The settings remain in 10+ separate settings pages with no multi-select to remove in bulk. I understand the risk to shared projects but having to do this level of housekeeping to remove a project is just overkill. I don't really understand the thinking that this is a good thing?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delete project and related schemes

David Meredith_lho1hy

Hi there,

Is there a way of moving a project to trash that also removes it's associated things get deleted:

Issue Type schemes
Issue Types (unused)
Screen Schemes
Screens
Workflow Schemes
Workflows
Field Configuration Schemes
Custom Fields
Issue Security Schemes
Notification Schemes
Permission Schemes

I've been going in and deleting these manually and frankly it's tedious... At the very least give me a multiselect tool so that I can bulk delete these unused items.

I hope that a better way of doing this exists. Please let me know.

Accepted answers

All comments

Robert Wen_Cprime_

Sorry, there's no feature I know of that does this. In fact, it may be a little dangerous if the fields and schemes are associated with more than one project.

Nic Brough -Adaptavist-

Indeed, that's exactly why the schemes and fields are not deleted with the projects - there's every chance that they

a) might be associated with other stuff

b) might need to be kept in case of mistakes

David Meredith_lho1hy

Hey guys,

The system knows what schemes etc is in use by what project. It shouldn't be too difficult for the system to identify the items that are shared with other projects and exclude those. Maybe present a screen that says warning, these workflows are shared with other projects, here be dragons.

AND ANOTHER THING... Why isn't there just a trash bin for these items? So if something does get deleted in error it can be restored appropriately?

I've seen a few feature requests for this but they don't have enough votes to see the light of production for a long time
https://jira.atlassian.com/browse/JRACLOUD-67882

Nic Brough -Adaptavist-

A lot of admins wouldn't want the schemes deleted automatically, they'd want to be able to turn that function off if it were ever implemented.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

project

cloud

delete

scheme

jira-service-management-cloud

jira-service-management