mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Tool Tips on status page status #3926
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3926
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RejectModders on GitHub (Jan 22, 2025).
📑 I have found these related issues/pull requests
I didn't see anything related to just
Tool Tips🏷️ Feature Request Type
Status-page
🔖 Feature description
Say you are on the status page, and someone has a status of
Server blah blahright? Maybe you have NO clue what that is, we add a thing for each one that has aDescriptionalready, that can be the tool tip, meaning you just need to add the logic for the tool tips and go off the description. I think that would be the best option in my opinion.But when you hover over the Name or something, it will display the description for that monitor.
✔️ Solution
Just to have an option in the backend to enable tool tips, default being on of course, and then it would just go off the description which is already a value in the backend dashboard.
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jan 3, 2026):
Regarding this issue:
I am not entirely sure which descriptions we currently have, where they are used and what the appropriate change would be.