Error when deleting components from the DB

[Milo Casagrande]

When trying to delete a component from the database via the admin interface, I was faced with a server error 500 page.
Digging a little bit into the code, looks like the component I was trying to delete didn't have any projects, or at least the associated Project object was None.

[Milosz Wasilewski (mwasilew)]

I just checked and this is a problem for all components. Attaching patch, that should fix it (at least until better solution is available)

[Milo Casagrande (milo)]

Milosz, patch looks good and is what I did locally on Friday, but didn't push anything in the repository.
The "problem" is that those fields in the model can be None, since they are set as Null=true, so we need to protect against that case in all the models.

[Milo Casagrande (milo)]

Patch pushed to master, and applied to production and staging. Manually applied, since to deploy status/roadmap we need to take the service down for maintenance a little bit more and do it correctly with ansible.

[Milosz Wasilewski (mwasilew)]

The problem here is that the burndown snapshot can be 'attached' either to project (global) or component (project). So we have to live with the blank=True in model definition or create separate models for each snapshot type.