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.

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

Use supported_enrollment_methods field to filter flows in digital/in-person views #2396

Closed
3 tasks
Tracked by #2261
thekaveman opened this issue Sep 23, 2024 · 0 comments · Fixed by #2420
Closed
3 tasks
Tracked by #2261
Assignees
Labels
back-end Django views, sessions, middleware, models, migrations etc.

Comments

@thekaveman
Copy link
Member

thekaveman commented Sep 23, 2024

We need to actually use this field! In the views that get the list of flows for the user to select from.

Originally posted by @thekaveman in #2383 (review)

Acceptance criteria

  • A flow that is digital-only shows up only on the digital side
  • A flow that is in-person only shows up only on the in-person side
  • A flow that supports both shows up on both sides
@thekaveman thekaveman added the back-end Django views, sessions, middleware, models, migrations etc. label Sep 23, 2024
@thekaveman thekaveman changed the title Use supported_enrollment_methods field to filter in digital/in-person views Use supported_enrollment_methods field to filter flows in digital/in-person views Sep 23, 2024
@machikoyasuda machikoyasuda self-assigned this Sep 23, 2024
@machikoyasuda machikoyasuda moved this from Todo to In progress in Digital Services Sep 23, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Digital Services Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end Django views, sessions, middleware, models, migrations etc.
Projects
Status: Done
2 participants