-
Notifications
You must be signed in to change notification settings - Fork 365
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
accurate-as-of should have both links go to the accurate-as-of page #4299
Comments
Alternatively, we could display a dialog on the feature detail page whenever the feature needs an accurate-as-of update and the signed in user is a feature owner. That would allow us to keep the same email format that is consistent with other emails that we send out, and also guide the user to the accurate-as-of form if they are just visiting the site for some other reason. I suppose that we could go further by adding the same dialog on all pages of the app, in addition to the feature detail page for that particular feature. It would need to be clear that the user is being asked to navigate to a different feature that they have responsibility for. cc: @jstenback |
I like the idea of surfacing the need to verify feature data in more places! |
Your alternative scenario sounds like a solid approach! Here's a more detailed breakdown: Alternative Scenario: Displaying a Dialog for Accurate-as-of UpdatesPrimary Scenario:
Alternative Scenario:
Steps:
Extended Alternative Scenario:
Benefits:
Considerations:
Would you like to discuss any specific implementation details or potential challenges? |
If a user gets an accurate-as-of reminder email, they might click the wrong link and go to the feature detail page. It would be better to eliminate that possible failure by making all links in the email message go to the accurate-as-of form. If the user wants to navigate to the feature detail page, they have ways to do that as a second step.
The text was updated successfully, but these errors were encountered: