Open Jesse-Box opened 1 year ago
@Jesse-Box IMO we can de-prioritize this part of the Acceptance Criteria:
I want to be notified only if any, all or no reports match Older or newer than a period of time Assigned to No one Team Specific member The latest release Specific key contains value ends with value equals value is set value does not contain value does not end with value does not equal value is not set value
Our main objective is to notify...
when there’s a new bug report from a project and or environment
@JoshFerge Would you agree? Trying to make sure I capture our convo from our last User Feedback sync here for clarity for Jesse.
This needs to be broken into N task tickets.
I think the starting point for figuring out how to build this out is to look at the existing Alert Wizard page, url is /alerts/wizard/
It looks like this:
An update on alerting as of today, which we plan to GA in 3 days.
User Feedbacks received from the new Widget the user can open are automatically alerted on.
Feedback from the 'crash report modal' or the User Feedback API in the SDKs that link to an error,(e.g Flutter) require users to opt-in on existant projects. Because we didn't want to introduce the risk of alerting folks who have high volume of feedback out of nowhere.
New projects have both enabled by default. (just verified that)
Problem
No way of being proactively notified of bugs
Acceptance Criteria
Designs