Issue Summary

Issue with marked_for_deletion of Repositories not being deleted in the Database.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Create a linked repo under Bamboo administration -> Linked repositories
2. Open a plan -> plan configuration -> Repositories -> Add a new repository (newly created in step 1)
3. Now delete the Linked repo from Bamboo administration -> Linked repo (global level) and we can see the marked_deletion as true. but won't be deleted as it has a dependency in the Plan configuration
4. Go to plan -> plan configuration -> Repositories -> delete the added repository and we can see that the marked_for_deletion is true and will be deleted from the database.

Expected Results

Once the dependent Repository gets deleted, it is expected to delete the parent/global repository which is marked_for_deletion=true.

Actual Results

The Global/parent repository remains in the database without deletion.

Workaround

Run an Expiry task, call it via the Bamboo UI via Bamboo Administration >> Expiry >> Run now or programmatically by calling the /rest/admin/latest/scheduler/jobs/trigger REST API endpoint with a command such as:

$ curl -u admin -p -H "Content-Type: application/json" -X POST -d '{"name": "ExpiryJob", "groupName": "ExpiryGroup"}' -k 'https://<Bamboo_URL>/rest/admin/latest/scheduler/jobs/trigger'