Multiple Incidents #1857

Closed
opened 2026-02-28 02:35:04 -05:00 by deekerman · 2 comments
Owner

Originally created by @HyperStreams on GitHub (Feb 6, 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

The ability to create multiple incidents for a status page. This would be good to have an Info incident and an incident if we needed to put an alert or warning up.

✔️ Solution

When you create an incident it currently removes the previous incident which was set. It would be great to have the ability to create another incident and unpin the ones we don't want.

Alternatives

An alternative could be to save previous incidents and have the ability to insert them after they've been unpinned.

📝 Additional Context

N/A

Originally created by @HyperStreams on GitHub (Feb 6, 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 The ability to create multiple incidents for a status page. This would be good to have an Info incident and an incident if we needed to put an alert or warning up. ### ✔️ Solution When you create an incident it currently removes the previous incident which was set. It would be great to have the ability to create another incident and unpin the ones we don't want. ### ❓ Alternatives An alternative could be to save previous incidents and have the ability to insert them after they've been unpinned. ### 📝 Additional Context N/A
Author
Owner

@chakflying commented on GitHub (Feb 6, 2023):

Tracked in #1253

@chakflying commented on GitHub (Feb 6, 2023): Tracked in #1253
Author
Owner

@CommanderStorm commented on GitHub (Dec 4, 2023):

@wnconnor
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #862 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 4, 2023): @wnconnor We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #862 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.
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#1857
No description provided.