Alternative to issue history #2013

Closed
opened 2026-02-28 02:40:15 -05:00 by deekerman · 4 comments
Owner

Originally created by @Appoxo on GitHub (Mar 18, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Ability to change the view of historical issues. Currently there is only a list of

Service Down Date #\1
Service Up Date #\1
Service Down Date #\2
Service Up Date #\2
Service Down Date #\3
Service Up Date #\3

✔️ Solution

A github like activity overview for daily/weekly/monthly/yearly for downtime (the grey dark/light green grid).
A live example for example for Reddit: https://www.redditstatus.com/uptime
image
This would make it more readable and create a better understanding how often a service was not responsive

Alternatives

No response

📝 Additional Context

No response

Originally created by @Appoxo on GitHub (Mar 18, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description Ability to change the view of historical issues. Currently there is only a list of ``` Service Down Date #\1 Service Up Date #\1 Service Down Date #\2 Service Up Date #\2 Service Down Date #\3 Service Up Date #\3 ``` ### ✔️ Solution A github like activity overview for daily/weekly/monthly/yearly for downtime (the grey dark/light green grid). A live example for example for Reddit: https://www.redditstatus.com/uptime ![image](https://user-images.githubusercontent.com/17850993/226106070-a482663b-7b63-4e97-80ad-1492812b4726.png) This would make it more readable and create a better understanding how often a service was not responsive ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
deekerman 2026-02-28 02:40:15 -05:00
Author
Owner

@CommanderStorm commented on GitHub (May 25, 2023):

@Appoxo is this a duplicate of #1984?
If not, please make this issue less similar by editing your issue.

@CommanderStorm commented on GitHub (May 25, 2023): @Appoxo is this a duplicate of #1984? If not, please make this issue less similar by editing your issue.
Author
Owner

@Appoxo commented on GitHub (May 25, 2023):

@Appoxo is this a duplicate of #1984?
If not, please make this issue less similar by editing your issue.

Can be considered a duplicate. Thank you :)

@Appoxo commented on GitHub (May 25, 2023): > @Appoxo is this a duplicate of #1984? > If not, please make this issue less similar by editing your issue. Can be considered a duplicate. Thank you :)
Author
Owner

@CommanderStorm commented on GitHub (May 25, 2023):

Can be considered a duplicate. Thank you :)

Could you then please close this issue? ^^

@CommanderStorm commented on GitHub (May 25, 2023): > Can be considered a duplicate. Thank you :) Could you then please close this issue? ^^
Author
Owner

@CommanderStorm commented on GitHub (Jun 11, 2023):

Thanks ❤️

@CommanderStorm commented on GitHub (Jun 11, 2023): Thanks ❤️
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2013
No description provided.