Clarify misleading warning text when posting a public note without a linked status page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- content
Research direction
Find the Preview notification modal and locate the warning shown when an incident has no status page. Update its copy to explain that no notifications will be sent and that the note may become visible if the incident is linked to a status page later. Confirm the displayed text matches the requested wording.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
When a user attempts to add a Public Note to an incident that is not yet linked to a status page, the Preview notification modal displays the following warning:"Nothing will be sent. No status page that lists these monitors will show this incident."
This copytext is misleading because - given the public note has been added, when a user retroactively connects this incident to a monitor and status page at a later time, the status page will actually show the note.
Describe the solution you'd like
No notifications will be sent
None of the monitors attached to this incident are visible on any status pages. If you link it to a status page later, this note may become visible.
- Dominant language
- TypeScript
- Stars
- 7.7k
- Forks
- 468
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 984
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OneUptime/oneuptime
-
bug follow-up
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
All issues in OneUptime/oneuptime
Similar issues
-
bug impact:low Team: SecuritySolution Team:Defend Workflows v9.6.0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
elastic/kibana#306401 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
agentes-chat/agentes-chat#927 ·
Maintainers usually reply within 1 day
-
comp/desktop P2 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#157702 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 1/5 Under an hour Newbie friendliness 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 comment ·
Maintainers usually reply within 1 day