-
Notifications
You must be signed in to change notification settings - Fork 19
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.
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
CM: Migrate existing Judge Teams to use Judge & Attorney Roles #12421
Comments
Estimating at 2. Do as a Rake task. |
…12636) Connects #12421 ### Description Creates a Rake task to process all the JudgeTeams and assign the Admin `JudgeTeamLead` and the nonadmins `DecisionDraftingAttorney`s. Will alert & not process empty judge teams, teams with no admin, teams with multiple admins. ## Test Plan Rake task run on dev without any issues. For production run, task should be run with `dry_run` and results reviewed before invoking final migration. Ultimately we are populating a currently empty table with data, and no data is being deleted. Risk is low.
Dry run in production found a small bug with passing in an argument for an alert message. Also discovered there are two extant judge teams with multiple admins already (!!). These two teams will not be affected by the rake task, and will be manually corrected instead as they are in what is currently considered a bad state. Notes:
|
Connects #12421 ### Description Invocation as well as definition.
Run in production. Log of the run can be found on slack Todo:
|
Followup to #12420 to update the existing JudgeTeams to mark their Judges & Attorneys before we add any new admins to teams.
Acceptance Criteria
JudgeTeamLead
DecisionDraftingAttorney
Part of #11801
The text was updated successfully, but these errors were encountered: