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

Issue template for agency configuration changes #2519

Open
9 tasks
thekaveman opened this issue Nov 12, 2024 · 0 comments
Open
9 tasks

Issue template for agency configuration changes #2519

thekaveman opened this issue Nov 12, 2024 · 0 comments
Labels
chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc.

Comments

@thekaveman
Copy link
Member

thekaveman commented Nov 12, 2024

Context

  • Changes for an agency that already exists in Benefits
  • New flows coming online, or modifications to existing flows (e.g. Digital only → Digital + In-person)
  • NOT for requesting copy changes

Information needed

This might actually be 2 templates? Could make it easier/more streamlined. Or maybe that would be more confusing for Customer Success...

New flow

  • Transit agency
  • Type of flow (Older Adult, Veterans, CalFresh, etc.)
  • Littlepay group ID
  • Expiration details if supported
  • Digital, In-person, or both
  • Plan for analytics/metrics -- requesting more of an acknowledgment that this has been considered

Existing flow

  • Transit agency
  • Type of flow (Older Adult, Veterans, CalFresh, etc.)
  • Changes requested

Intended process

  1. Customer Success Account Manager (AM) is in contact with the agency, communicating what options are available in Benefits
  2. Agency requests e.g. a new flow enabled for them in Benefits
  3. AM fills out ticket using this template
  4. Devs assign and work on ticket for test environment
  5. Devs notify AM that flow is ready for review in test
  6. AM works with agency to review flow in test
  7. AM notifies devs that flow is approved in test
  8. Devs work on ticket for prod environment
  9. Devs release/deploy/configure and close ticket
  10. Devs notify AM that configuration is live in prod
@thekaveman thekaveman added the chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc. label Nov 12, 2024
@thekaveman thekaveman moved this from Todo to Stretch in Digital Services Nov 12, 2024
@thekaveman thekaveman moved this from Stretch to Needs shaping in Digital Services Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Chores and tasks for code cleanup, dev experience, admin/configuration settings, etc.
Projects
Status: Needs shaping
Development

No branches or pull requests

1 participant