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

Launch MST Courtesy Cards Feature #608

Closed
34 tasks done
vykster opened this issue May 20, 2022 · 4 comments
Closed
34 tasks done

Launch MST Courtesy Cards Feature #608

vykster opened this issue May 20, 2022 · 4 comments
Labels
epic Issues that document a large set of features and/or decisions

Comments

@vykster
Copy link
Member

vykster commented May 20, 2022

Date: Friday May 20th 2022
Writers: @thekaveman @vykster
Status: Complete - Released and Deployed on Monday, November 14
Priority: No. 1 per the Roadmap

Associated Milestone: https://github.com/cal-itp/benefits/milestone/13

Background

Monterey-Salinas Transit (MST) has its own in-house system for issuing identification cards called Courtesy Cards. the associated database is called Velocity. This feature will allow any rider who has already been issued a physical Courtesy Card the ability to associate their status as a card holder with a contactless open-loop credit card and participate in the contactless demo while paying their discounted-fare.

Definition of Done

New releases of Benefits and Eligibility Server are published with release notes.

Acceptance criteria

  • The Benefits application is configured to support verification of MST Courtesy Card status
  • An instance of the Eligibility Server is configured with MST's Courtesy Card data
  • MST's Courtesy Card system is configured to sync new data to the Eligibility Server instance regularly
  • MST approves of the general user flow
  • MST Customer Service has the resources to support their customer's questions
  • A user can navigate to benefits.calitp.org/mst, (optionally) select to verify with their Courtesy Card, successfully verify a valid Courtesy Card number, and continue on to enroll their contactless payment card with Littlepay

User Stories

Tasks

Server


Benefits


Operations


Product

Implementation Ready Checklist

  • Acceptance criteria defined
  • Team understands acceptance criteria
  • Acceptance criteria is verifiable
  • User workflows defined / designed
  • External / 3rd Party dependencies identified

Links, resources

@thekaveman thekaveman added the epic Issues that document a large set of features and/or decisions label May 20, 2022
@thekaveman thekaveman added this to the Courtesy Cards milestone May 20, 2022
@thekaveman thekaveman pinned this issue May 20, 2022
@cal-itp cal-itp deleted a comment from vykster May 20, 2022
@machikoyasuda machikoyasuda unpinned this issue Jun 6, 2022
@vykster vykster pinned this issue Jun 6, 2022
@vykster
Copy link
Member Author

vykster commented Nov 1, 2022

@thekaveman would it be appropriate to add a task for write/publish release notes to this epic?

@thekaveman
Copy link
Member

@vykster we certainly could - it's one of the tasks in our Issue Template for Making a Release so will be tracked as part of that. I suppose a specific task to write the notes might be useful?

It's related to one thing I wanted to talk about process-wise / suggest a change: I'd like us to stop listing out all the individual tasks on the Epics, since they are all associated with a Milestone anyway, it makes for multiple places to keep updated.

@machikoyasuda
Copy link
Member

UAT on dev-benefits.calitp.org/ is complete. Thank you @MarikoLochridge

Release to test-benefits.calitp.org/ is happening today. Tracked in #1124

Release to prod planned for Monday.

@machikoyasuda
Copy link
Member

MST CC feature has been released by @angela-tran and me on Monday, November 14th

benefits.calitp.org/

@thekaveman thekaveman unpinned this issue Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Issues that document a large set of features and/or decisions
Projects
Archived in project
Development

No branches or pull requests

3 participants