[Event Timestamps] Enhance Experience Around High Latency Events
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 624
Description
### Problem Statement
From the customer:
> It feels like there lots of room for improvement with the terminology used on the alerts and issues screens. An issue shows two dates, "occurred" for when for the time the issue took place on the device, and received for when the issue was uploaded and processed by sentry.
Regarding the wording on "WHEN" condition of Alert rulkes:
> It sounds like `The event occurs` is more like `The event is received`.
Regarding the wording on ignoring an issue:
> "Ignore until this occurs again one time from now” is more like "Ignore until another event is receved one time from now"
### Solution Brainstorm
Align the terminology on these fields with the actual behavior.
### Product Area
Issues
Contributor guide
Assessment
This issue has not been assessed yet.