-
Suggestion
-
Resolution: Unresolved
-
779
-
145
-
Hi everyone,
Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.
We are actively working on a solution for this feature request. Our team is committed to thoroughly investigating the best way to address this need, and we will keep you informed as we get closer to a possible release date.
Thank you to every person who provided feedback on this issue. We will update you as soon as we have more concrete information to share.
Joe Nguyen
jnguyen2@atlassian.com
Product Manager - Jira Cloud
Summary
When deleting projects that include thousands of issues and attachments, it might take more time than expected, causing delays in migrations or other situations where deleting the data is needed.
Expected Results
Deleting huge projects is expected to be a long process, but it could definitely, be improved, as sometimes can take many hours.
Actual Results
Deleting the projects huge be faster and provide an expected time for when they are going to be fully deleted.
- is related to
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
JRACLOUD-83038 Attaching thousands of files to a single issue can lead to concurrency issues during project deletion.
-
- Closed
-
-
JST-925417 You do not have permission to view this issue
- links to
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PIR - Improvement Action
-
[JRACLOUD-80059] Improve Performance in Deleting Huge Projects
Aside from taking too long, and blocking a migration while the deletion is in progress ... there isn't an indication that the delete has actually been requested.
Also ... what happens when you request deletion, and then request that the project be restored. Is the deletion request still in progress...? I went through the whole Trash -> Delete -> Restore -> Trash -> Delete again ... and had no feedback as to what was actually happening under the hood.
Our project with ~120000 issues took over 30 hours to be deleted from Trash. This needs to be improved.
Our project with 60.000 issues and 16gb data took around 27 hours. That's too long.
I am having the same issue with deleting a 4gb project which took around 1,5h. It would at least be useful to change the dialogue text so I am prepared for the wait time.
A bit a context: it took 15h to delete a project of 15GB. This project was badly migrated and was blocking the second run of our migration. So clearly it was a problem for us as the migration had to be finished during a week-end.
I am also facing the same issue. It is taking too much time to delete just 35961 issues. It has been more than 12 hours and still the project present in Trash. This is frustrating and becomes a bottleneck of my entire migration activity. Jira Cloud team should look into it on priority basis.