Surge Alert Status and Ordering based on status and opens fields

[susilnem]

Addresses

• Implement ordering on the Surge Alert table based on status and opens fields #2036

Changes

• Add Status Field in Alert
• Add status in enums
• Create Cronjob Command to update the Alert status

Post deployment actions

@szabozoltan69 We need to run this after deployment to update the status. After that, it will be updated every 12 hours.

./manage.py update_surge_alert_status

Checklist

Things that should succeed before merging.

• Updated/ran unit tests
• Updated CHANGELOG.md

Release

If there is a version update, make sure to tag the repository with the latest version.

[k9845]

lets add test case as well

[thenav56]

Looks good. Few comments

[thenav56]

Hey @szabozoltan69, could you review and merge/deploy this to staging?

[thenav56]

Hey @szabozoltan69

We also need to run this after deployment to initiate the status. After that, it will be updated every 12 hours.

./manage.py update_surge_alert_status

[szabozoltan69]

Hey @thenav56
Deployment to Staging was ok, also the migration:
Running migrations:
Applying notifications.0014_surgealert_status... OK
Also this was run flawless:
./manage.py update_surge_alert_status

[k9845]

@szabozoltan69 Can you run ./manage.py update_surge_alert_status command on production? I think we missed this.

[szabozoltan69]

Now I did it.