-
Notifications
You must be signed in to change notification settings - Fork 0
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
Question: Recommended Statuses Descriptions For Notifications #32
Comments
Recommendation from Exec 7/9 after our kickoff: MVP should include two statuses, at minimum: "filed" and "in public review". "Completed" is not necessary, and neither are individual milestones on any project. TBD on "noticed" |
Thanks for the update! Would the status descriptions follow what we currently have for ZAP or are they flexible to change?
We are trying to gauge how informative these descriptions should be as the impact the information sent out in notifications (hence the reason we suggest including a status page to provide a resource for more info in case the notifications are a simpler format). |
The "In public review" status description should be fine (though recommend removing the "certification" piece of it since there's more than one way into public review). We'll need to work on the one for "filed" since it doesn't exist on ZAP Search. Let's think more about the utility of a status page as we also think about what the notification actually says and where it links. Open to all suggestions. |
Whichever statuses/milestones we support for MVP, they will be "all or nothing", correct? As in, users wouldn't be able to sign up for "Filed" but not "In Public Review". I'll have my team investigate if it's feasible to use the project statuses seen in ZAP Search to drive the notifications. I'm not sure if the data tells us when a project went from one status to another, as opposed to milestones where we can query dates that given project milestones where marked as "completed". |
Correct, Tyler. "All or nothing" would be preferred when users sign up for these updates. Thank you! |
And querying milestone completions as a marker of status notifications is fine. Apologies if I made that confusing. I meant that for a status definition, using the same one that's on ZAP Search is fine for in public review. I.e., these are applications that have graduated to the public review process. We can workshop this language and give you final wording ahead of a due date if you want to define one. |
From today's meeting 7/17: Leaning toward one and do not let user choose one.
|
More notes from 7/17 brainstorming:
|
To clarify what statuses would are strongly recommended to be in the MVP and what description/information that should come along with a status. We currently using our notify flow diagram to illustrate what we think would be recommended areas to be notified during the application process.
Questions:
The text was updated successfully, but these errors were encountered: