[Feature]: Incident Timeline

juadams commented 2 years ago

🏷️ Feature Request Type

UI Feature

🔖 Feature description

It would be great to have a scrolling timeline of incidents by date on the status page, even just the last X months or something.

Said incident timeline should include:

different statuses, descriptions and the timestamp
fit into the current design lanuage A draft from #1253:

✔️ Solution

Similar to how StatusPage has it.

See DropBoxs' status page "past incidents"

❓ Alternatives

No response

📝 Additional Context

https://status.dropbox.com/

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

[X] I checked and didn't find similar feature request

Stage4000 commented 2 years ago

Alternatives: Allow for multiple incidents instead of just one, change unpin to delete.

bradhawkins85 commented 2 years ago

It would be great to have both past incidents and multiple incidents features added. Would it also be possible to link the incident to a service, which would allow users to click on the service and filter down to a list of incidents for that one service and/or it would show the service name in the past incidents list

agateblue commented 2 years ago

We're looking for a way to communicate about incident resolution and impact with our clients. The current incident system is great for real-time updates, but doesn't work well when you need to write down and share long-form information about a given incident, since an unpinned entry simply disappear and cannot be found again.

A dedicated timeline with a permalink for each incident would solve the issue for us. I may give it a go in the upcoming months if nobody starts working on this in the meantime :)

karelkryda commented 2 years ago

Hi, I'm currently working on new incident system.

This is the screen for creating a new incident. In the details of the incident, it will be possible to add updates to the status of the incident (investigation, problem found, solved, ...). Please feel free to offer your ideas, features and overall functionality. I will try to add everything you need. 🙂

juadams commented 2 years ago

From the screenshot, it looks like it's coming along nicely! It would be nice to have a resolved or not option. So the incident can keep its original type, but can be seen as resolved or not, of course open to thoughts and opinions on this. My idea is that if a history is implemented someone could audit the incidents for something like "Listing all critical incidents with more than 1 hour to resolve"

Thank you for putting your time and effort into this!

Cheers, Justin

On Mon, Jan 31, 2022 at 10:16 AM Karel Krýda @.***> wrote:

Hi, I'm currently working on new incident system.

[image: image] https://user-images.githubusercontent.com/59953812/151804218-c5083134-f4e6-4c49-b8fb-a8be694c8237.png This is the screen for creating a new incident. In the details of the incident, it will be possible to add updates to the status of the incident (investigation, problem found, solved, ...). Please feel free to offer your ideas, features and overall functionality. I will try to add everything you need. 🙂

— Reply to this email directly, view it on GitHub https://github.com/louislam/uptime-kuma/issues/862#issuecomment-1025755663, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC2TNRVVUMMJQFVNE5N2PP3UY2HEXANCNFSM5HFP5U3A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

karelkryda commented 2 years ago

I hope to have it done today 🙂

agateblue commented 2 years ago

Thank you @karelkryda this looks very good!

sgeneralgrievous commented 1 year ago

has this been added yet?

0xgui commented 1 year ago

How is the status of this feature ?

CommanderStorm commented 1 year ago

@eazylaykzy @0xgui @sgeneralgrievous Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder and adds no productivity. We use 👍🏻 on issues to prioritise work. See #1253 for the status

Lanhild commented 5 months ago

@CommanderStorm Some ideas for this feature

The incident timeline should also include maintenances if monitors on the status page were affected
https://github.com/louislam/uptime-kuma/pull/4565
Have the timeline accessible by a link, in a fashion similar to Atlassian's, only showing days where incidents occured Have the timeline be on a different slug such as /status/your-page/history. That way we'd be able to link directly to the incidents page

Lanhild commented 1 month ago

Here is another design example: https://status.appwrite.online/incidents

louislam / uptime-kuma