Currently, the signature's `application` fields are nullable. This contradicts [Django's official conventions](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.null) & doesn't allow us to integrate it in the siganture's `unique_contraints`. We need to make the field non-nullable & default it to either 'unspecified' or empty string ''.
Bug 1625451 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Currently, the signature's `application` fields are nullable. This contradicts [Django's official conventions](https://docs.djangoproject.com/en/3.0/ref/models/fields/#django.db.models.Field.null) & doesn't allow us to integrate it in the siganture's `unique_contraints`. We need to make the field non-nullable & default it to either 'unspecified' or empty string ''. If this will require some prior data migrations, we should file a separate bug for that & treat it as a blocker for this one.