Skip to content

Commit 7127b2e

Browse files
🐛 Fix db_migration fix_available field to allow None (#12817)
* 🎉 Make fix_available field available for deduplication * fix
1 parent e50a954 commit 7127b2e

2 files changed

Lines changed: 3 additions & 2 deletions

File tree

dojo/db_migrations/0238_finding_fix_available.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,6 @@ class Migration(migrations.Migration):
1313
migrations.AddField(
1414
model_name='finding',
1515
name='fix_available',
16-
field=models.BooleanField(default=True, help_text='Denotes if there is a fix available for this flaw.', verbose_name='Fix Available'),
16+
field=models.BooleanField(default=None, help_text='Denotes if there is a fix available for this flaw.', null=True, verbose_name='Fix Available'),
1717
),
1818
]

dojo/models.py

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2404,7 +2404,8 @@ class Finding(models.Model):
24042404
null=True,
24052405
blank=True,
24062406
help_text=_("Text describing how to best fix the flaw."))
2407-
fix_available = models.BooleanField(default=True,
2407+
fix_available = models.BooleanField(null=True,
2408+
default=None,
24082409
verbose_name=_("Fix Available"),
24092410
help_text=_("Denotes if there is a fix available for this flaw."))
24102411
impact = models.TextField(verbose_name=_("Impact"),

0 commit comments

Comments
 (0)