starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Implement Dropdown Menu for Accessing incident templates #3182

New issue

Open

opened 2026-02-28 03:20:51 -05:00 by deekerman · 8 comments

deekerman commented

2026-02-28 03:20:51 -05:00

Owner

Originally created by @LeoThies on GitHub (Mar 11, 2024).

There are some incidents that often repeat. Therefore, we would like to implementing a dropdown menu for previous incidents.

🏷️ Feature Request Type

Status-page

🔖 Feature description

To streamline our process and reduce redundancy, we're would like to implement a feature that archives previous incidents. This will enable us to access past incidents with fewer clicks, eliminating the need to retype the same text repeatedly.

✔️ Solution

Upon selecting 'Templates,' a list should appear featuring either previous incidents or saved incidents.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @LeoThies on GitHub (Mar 11, 2024). ### 📑 I have found these related issues/pull requests There are some incidents that often repeat. Therefore, we would like to implementing a dropdown menu for previous incidents. ### 🏷️ Feature Request Type Status-page ### 🔖 Feature description To streamline our process and reduce redundancy, we're would like to implement a feature that archives previous incidents. This will enable us to access past incidents with fewer clicks, eliminating the need to retype the same text repeatedly. ### ✔️ Solution ![templates](https://github.com/louislam/uptime-kuma/assets/115998386/0931af03-63b9-4aac-ba06-aa12787d6f30) Upon selecting 'Templates,' a list should appear featuring either previous incidents or saved incidents. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:incidents

labels

2026-02-28 03:20:51 -05:00

deekerman commented

2026-02-28 03:20:55 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Mar 11, 2024):

I would need to look up if we save incidents somewhere in the database.
In any case this would be a larger feature. If you'd like to implement this, please first start of with a plan what you would like to add where ("How should this work") via annotated screenshots and what database modifications are needed to get there.
Here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

Note that for larger features our pipeline is currently quite full already
=> I don't know when we would get to this.

Note to self:
I think the guidance on new features in our contribution guide is pretty lacking => we defintively need to improve that part ^^

@CommanderStorm commented on GitHub (Mar 11, 2024): I would need to look up if we save incidents somewhere in the database. In any case this would be a larger feature. If you'd like to implement this, please first start of with a plan what you would like to add where ("How should this work") via annotated screenshots and what database modifications are needed to get there. Here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md Note that for larger features our pipeline is currently quite full already => I don't know when we would get to this. Note to self: I think the guidance on new features in our contribution guide is pretty lacking => we defintively need to improve that part ^^

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@Lanhild commented on GitHub (Apr 17, 2024):

@CommanderStorm There is a table named incident. The status page UI indeed could benefit from an incident history

@Lanhild commented on GitHub (Apr 17, 2024): @CommanderStorm There is a table named `incident`. The status page UI indeed could benefit from an incident history

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@Lanhild commented on GitHub (Apr 17, 2024):

In any case this would be a larger feature. If you'd like to implement this, please first start of with a plan what you would like to add where ("How should this work") via annotated screenshots and what database modifications are needed to get there.

For me, this issue should be divided in two;

Ability to view past incident in the respective status page
Ability to create incident templates

what database modifications are needed to get there.

None for (1). As the incident table already exists and features everything needed for this feature to work.
A new incident_template table to store incident templates.

@CommanderStorm should we open new issues to divide these like I explained?

@Lanhild commented on GitHub (Apr 17, 2024): > In any case this would be a larger feature. If you'd like to implement this, please first start of with a plan what you would like to add where ("How should this work") via annotated screenshots and what database modifications are needed to get there. For me, this issue should be divided in two; 1. Ability to view past incident in the respective status page 2. Ability to create incident templates > what database modifications are needed to get there. - None for (1). As the `incident` table already exists and features everything needed for this feature to work. ![image](https://github.com/louislam/uptime-kuma/assets/73610779/fb87cf8f-839f-4dfc-9396-c276b6ab5a39) - A new `incident_template` table to store incident templates. @CommanderStorm should we open new issues to divide these like I explained?

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 17, 2024):

Ability to view past incident in the respective status page

I am going to reference a related PR which did not work our mostly because of being too big to review

https://github.com/louislam/uptime-kuma/pull/1253

=> "stealing" (keep the authorship) incident list from said PR might be a good starting point (keep it simple, no 4k changed lines please, that is not reviewable)
=> the correct issue (forgot to deduplciate in the last comment) is https://github.com/louislam/uptime-kuma/issues/862

Lets forcus in this issue only on incident-templates keep this on-track ^^

@CommanderStorm commented on GitHub (Apr 17, 2024): > Ability to view past incident in the respective status page I am going to reference a related PR which did not work our mostly because of being too big to review - https://github.com/louislam/uptime-kuma/pull/1253 => "stealing" (keep the authorship) incident list from said PR might be a good starting point (keep it simple, no 4k changed lines please, that is not reviewable) => the correct issue (forgot to deduplciate in the last comment) is https://github.com/louislam/uptime-kuma/issues/862 Lets forcus in this issue only on incident-templates keep this on-track ^^

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 17, 2024):

incident_template table to store incident templates

Sounds good so far, what do you think would be a good modeling?

status page 1<-n incident_template
status page n<->m incident_template

@CommanderStorm commented on GitHub (Apr 17, 2024): > `incident_template` table to store incident templates Sounds good so far, what do you think would be a good modeling? - status page 1<-n `incident_template` - status page n<->m `incident_template`

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@Lanhild commented on GitHub (Apr 17, 2024):

How is the template linked to the status page itself? The only relation I see is between the template and the incident?

@Lanhild commented on GitHub (Apr 17, 2024): How is the template linked to the status page itself? The only relation I see is between the template and the incident?

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 17, 2024):

Them being global is fine by me. Don't think there needs to be a relation between incidents and templates (what would we use it for?)

What I am currently a bit torn is if adding/removing of templates should be done in the settings or in the same modal to select the template.

@CommanderStorm commented on GitHub (Apr 17, 2024): Them being global is fine by me. Don't think there needs to be a relation between incidents and templates (what would we use it for?) What I am currently a bit torn is if adding/removing of templates should be done in the settings or in the same modal to select the template.

deekerman commented

2026-02-28 03:20:56 -05:00

Author

Owner

@Lanhild commented on GitHub (Apr 17, 2024):

What I am currently a bit torn is if adding/removing of templates should be done in the settings or in the same modal to select the template.

I think the better thing would be to have it in the same modal. When writing an incident, you'd fill whatever info and have the option to save it as a template

@Lanhild commented on GitHub (Apr 17, 2024): > What I am currently a bit torn is if adding/removing of templates should be done in the settings or in the same modal to select the template. I think the better thing would be to have it in the same modal. When writing an incident, you'd fill whatever info and have the option to save it as a template