-
Notifications
You must be signed in to change notification settings - Fork 9
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
Clean up EnrollmentFlow
labels in dev, test, and prod to remove prefix
#2511
Comments
@lalver1 I noticed while working on #2503 and #2510 that in test, the Nevada County flows were created with labels that are prefixed with Doing this ticket will help ensure no one is mislead by labels lingering around with the old pattern. Note this ticket is not on the sprint, so should be worked on if we finish all sprint items or during slush time. |
Updated flow labels in test-benefits.calitp.org/adminNote: while updating these, I read the system names and labels for the Nevada County Connects in-person flows more closely. Are these the correct values? I'd like to avoid us accidentally using inconsistent values and having to do analytics data clean-up later. (I've only heard of us planning to use At the very least, I removed the Values in question:
#2434 is the corresponding configuration ticket for these values. BeforeAfter |
Done with configuration changes. I'll raise the question about those flows in test-benefits outside of this issue when we come back from break. |
Acceptance Criteria
Additional context
With #2403 merged in, we don't need to have a prefix in the label of
EnrollmentFlow
s that says which transit agency the flow is for; the table shows us that information already.Also, recall that the
EnrollmentFlow
's label is used as the text for the radio buttons when selecting a transit benefit during in-person enrollment. So in general, the label should be what we want the users of Benefits Administrator to see.More specifically, if the flow is digital, we should use the same copy as what's in the flow's
selection_label_template
, e.g. for Medicare flows, we'd want to use "Medicare Cardholder" since that's what's in the selection label template.#2336 is the ticket that this configuration change corresponds to.
The text was updated successfully, but these errors were encountered: