Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

remove old OutcomeOrder model #1820

Open
actlikewill opened this issue May 21, 2024 · 3 comments · May be fixed by #1825
Open

remove old OutcomeOrder model #1820

actlikewill opened this issue May 21, 2024 · 3 comments · May be fixed by #1825
Assignees
@actlikewill
Labels
impact: low ops Operations

Comments

@actlikewill
Copy link
Contributor

actlikewill commented May 21, 2024 •
edited
Loading

remove the old model after successful deployment of the change
@actlikewill
Copy link
Contributor Author

@niiroobiro I think this will affect some of the metabase dashboards. You may want to double check if any dashboards use the OrderOutcome model and update them before I remove the model.

@niiroobiro
Copy link
Contributor

okay.

@actlikewill actlikewill linked a pull request May 24, 2024 that will close this issue
Draft
@niiroobiro
Copy link
Contributor

Outcomes:

  • Appeal allowed
  • Appeal dismissed
  • Application dismissed
  • Appeal partially allowed
  • Application granted

The rest should be orders.

@actlikewill actlikewill self-assigned this Jun 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@actlikewill actlikewill

Labels
impact: low ops Operations
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove OrderOutcome model laws-africa/peachjam
3 participants
@longhotsummer @actlikewill @niiroobiro