If you are looking for issues to work on, here are some issues organized by priority:

• High Priority
• Normal Priority
• Low Priority

(most of these are not simple straightforward issues; there are some nice small, but more complicated issues

During an upgrade of the Kubernetes package versions in PR #636 a bunch of context.TODO() function call parameters were added. We should go through and plug these into any existing contexts we have and implement new contexts for the others.

Should be able to click on the service:

and get a modal with the following information:

• Request URL
• Request body
• (?) Last failure recorded (new field in service)
• Alerting information (if #2 has been implemented)

Is your feature request related to a problem? If so, please describe the problem:
We have an established set of queries and processes for determining how complete data collection is. They rely on at least one run of the repo_info worker, as we validate what Augur collects against platform (github/gitlab) metadata.

Potential solutions:
These are the queries and shell commands:

[cu

⚠️ IMPORTANT: Please fill out this template to give us as much information as possible to consider/implement the feature.

Prerequisites

• check this box if you have completed the following:
  • Reviewed the contributing guidelines and [support](https://github.com/COVID-19-electronic-healt

at the moment if we scaffold an app with a charfield with choices field it will put in an input field, lets use a radio field

This issue contains our weekly progress updates.
(we have a project but it's not great for viewing history)

Until we opened this issue, we had been conducting our standups verbally ...
But as we all know, ephemeral project management is terrible for personal/team accountability.

Steps to participate:

1. Ensure that the issue you are w