Currently in AbstractProject, when performDelete is called, it will call makeDisabled first, and makeDisabled will check if supportsMakeDisabled is true, if supportsMakeDisabled is true, all queued items will be canceled. What performDelete should really do is regardless supportsMakeDisabled is true or false, all queued items for the project needed to be canceled.

Currently behavior will cause all jobs stuck in the queue. If a project got deleted, but it has job in the queue, and queued job is not canceled, all job after that will be queued and won't be run unless manually cancel the deleted job.