A complete maintenance planning system #1213

karelkryda · 2022-01-23T14:41:28Z

Description

This pull request includes the addition of maintenance planning functionality.

Affected monitors are not tested during maintenance, but status "3" (MAINTENANCE) is returned.
No notifications are also sent during maintenance. Notifications will only be sent if the monitor status after maintenance is "DOWN" (MAINTENANCE -> DOWN).

Due to the addition of this function, the UI has also been changed (adding buttons, texts, ...).

This pull request also requires the addition of some new translations.

Related issue: #191

Type of change

Please delete any options that are not relevant.

User interface (UI)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected) - shouldn't

Checklist

My code follows the style guidelines of this project
I ran ESLint and other linters for modified files
I have performed a self-review of my own code and tested it
I have commented my code, particularly in hard-to-understand areas
My changes generate no new warnings
My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Saibamen · 2022-01-23T16:24:55Z

server/model/maintenance.js

+            title: this.title,
+            description: this.description,
+            start_date: this.start_date,
+            end_date: this.end_date


For better git diff in next updates to this object

Suggested change

end_date: this.end_date

end_date: this.end_date,

Saibamen · 2022-01-23T16:25:01Z

server/model/maintenance.js

+            title: this.title,
+            description: this.description,
+            start_date: this.start_date,
+            end_date: this.end_date


Suggested change

end_date: this.end_date

end_date: this.end_date,

Saibamen · 2022-01-23T16:25:28Z

server/model/monitor.js

@@ -6,7 +6,7 @@ dayjs.extend(utc);
 dayjs.extend(timezone);
 const axios = require("axios");
 const { Prometheus } = require("../prometheus");
-const { debug, UP, DOWN, PENDING, flipStatus, TimeLogger } = require("../../src/util");
+const { debug, UP, DOWN, PENDING, MAINTENANCE, flipStatus, TimeLogger} = require("../../src/util");


Suggested change

const { debug, UP, DOWN, PENDING, MAINTENANCE, flipStatus, TimeLogger} = require("../../src/util");

const { debug, UP, DOWN, PENDING, MAINTENANCE, flipStatus, TimeLogger } = require("../../src/util");

Saibamen · 2022-01-23T16:27:20Z

server/routers/api-router.js

@@ -5,7 +5,7 @@ const server = require("../server");
 const apicache = require("../modules/apicache");
 const Monitor = require("../model/monitor");
 const dayjs = require("dayjs");
-const { UP, flipStatus, debug } = require("../../src/util");
+const { UP, MAINTENANCE, flipStatus, debug} = require("../../src/util");


Suggested change

const { UP, MAINTENANCE, flipStatus, debug} = require("../../src/util");

const { UP, MAINTENANCE, flipStatus, debug } = require("../../src/util");

Saibamen · 2022-01-23T16:29:45Z

src/components/MonitorList.vue

@@ -47,7 +66,7 @@
 import HeartbeatBar from "../components/HeartbeatBar.vue";
 import Uptime from "../components/Uptime.vue";
 import Tag from "../components/Tag.vue";
-import { getMonitorRelativeURL } from "../util.ts";
+import {getMaintenanceRelativeURL, getMonitorRelativeURL} from "../util.ts";


Suggested change

import {getMaintenanceRelativeURL, getMonitorRelativeURL} from "../util.ts";

import { getMaintenanceRelativeURL, getMonitorRelativeURL } from "../util.ts";

Saibamen · 2022-01-23T16:36:18Z

src/pages/EditMaintenance.vue

+                Object.values(this.$root.monitorList).map(monitor => {
+                    this.affectedMonitorsOptions.push({
+                        id: monitor.id,
+                        name: monitor.name


Suggested change

name: monitor.name

name: monitor.name,

Saibamen · 2022-01-23T16:36:29Z

src/pages/EditMaintenance.vue

+
+        "$route.fullPath"() {
+            this.init();
+        }
+


Suggested change

"$route.fullPath"() {

this.init();

}

"$route.fullPath"() {

this.init();

}

Saibamen · 2022-01-23T16:36:51Z

src/pages/EditMaintenance.vue

+            }
+
+        },


Suggested change

}

},

}

},

Saibamen · 2022-01-23T16:37:12Z

src/pages/EditMaintenance.vue

+            this.processing = true;
+
+            if (this.affectedMonitors.length === 0) {
+                toast.error(this.$t("Select at least one affected monitor"));


Shorter i18n key

Saibamen · 2022-01-23T16:40:06Z

src/pages/EditMaintenance.vue

+
+                            <!-- Start Date Time -->
+                            <div class="my-3">
+                                <label for="start_date" class="form-label">{{ $t("Start of maintenance") }}</label>


It will be good to add current timezone in label?

Did you mean this way?

I see, for example, that heartbeats are stored in UTC format. Should I convert user input to UTC format and use the "old" datetime() function?

No, in label, not in input...

For example:

Start of Maintenance (GMT+1) <input ...>

I understand. I will now commit with minor fixes (missing commas, spaces, translations) and try to make some adjustments to storing maintenance dates in the database.

Currently, the date is stored in the database in the time zone in which the date was entered by the user, not in UTC (+0) format, so it cannot be converted to the current time zone, eg when changing the time zone.
Ie. if the user enters 1:35 while creating maintenance and changes the time zone, it will still show 1:35.

Saibamen · 2022-01-23T21:23:29Z

server/model/monitor.js

@@ -28,9 +29,12 @@ class Monitor extends BeanModel {
     * Only show necessary data to public
     */
    async toPublicJSON() {
+        const maintenance = await R.getAll("SELECT mm.*, maintenance.start_date, maintenance.end_date FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now', 'localtime') AND datetime(maintenance.end_date) >= datetime('now', 'localtime')", [this.id]);


We have 3 this same queries in this file, 4th this same query is in api-router.js

I understand, can I ask your opinion?

The states of individual monitors are currently evaluated according to the state of the last heartbeat.
If I used this system in case of maintenance, any change in the maintenance settings (adding / removing the monitor from maintenance, changing the maintenance time) would not affect the monitor and the status page until the next heartbeat of the monitor.
By directly checking whether or not the monitor is in maintenance, it is possible to mark the monitor as in maintenance before a heartbeat occurs.
For this reason, this SQL query is also called when requesting monitor information instead of being called only twice (on the status page and at heartbeat).

In my opinion, this is more user-friendly, because the fact that the monitor is in maintenance or not can be seen immediately without waiting, even on the status page.

Do you think it will be better to leave the status display according to the last heartbeat, or do you find the my current solution better?

Thanks for the feedback

IMO your (current) solution is better

Thank you for your feedback.

In this case, 2 out of 4 calls are absolutely necessary (calls from the status page - display of maintenance information on the status page and at each beat - finding out if the monitor is under maintenance) and if I am not mistaken, in the methods "toJSON()" and "toPublicJSON()" this calls are also required to let the current solution described above work.

If I'm wrong, feel free to tell me your opinion.

Thank you

I don't know . I just wanted to have this long query-code line in one place (helper function etc)

Oh, understand. It shouldn't be problem I think, I think I'll be able to move it into one helper function and just call it.

Few minutes later I commited some changes, so I'll check / do this tomorrow I guess.

Done. It's now in its own method.

Saibamen · 2022-01-23T21:26:17Z

src/components/MonitorList.vue

@@ -47,7 +66,7 @@
 import HeartbeatBar from "../components/HeartbeatBar.vue";
 import Uptime from "../components/Uptime.vue";
 import Tag from "../components/Tag.vue";
-import { getMonitorRelativeURL } from "../util.ts";
+import {getMaintenanceRelativeURL, getMonitorRelativeURL } from "../util.ts";


Suggested change

import {getMaintenanceRelativeURL, getMonitorRelativeURL } from "../util.ts";

import { getMaintenanceRelativeURL, getMonitorRelativeURL } from "../util.ts";

…ch allows it to be converted between time zones

… in its own method.

karelkryda · 2022-01-28T08:56:51Z

@Saibamen, Everything should be OK 🙂

Saibamen · 2022-01-28T16:14:30Z

@louislam

mathiskir · 2022-02-19T12:58:20Z

Seems like this isn't working.
When trying to create a new monitor, it throws this:

installed with git clone -b master https://github.com/karelkryda/uptime-kuma && cd uptime-kuma && npm ci && npm run build && node server/server.js
No errors in console
This problem was on my end, works now!
@louislam

karelkryda · 2022-02-19T13:01:29Z

@mathiskir make sure you removed folder with previous clone. Remove whole uptime-kuma folder, clone and try again, please

mathiskir · 2022-02-19T13:14:54Z

It works!

mathiskir · 2022-02-19T19:28:06Z

This + #1253 + #1236 + a rest API to push incidents and maintenances would make uptime kuma fire

nocturn9x · 2022-03-01T11:11:05Z

We need more people with access to the repo so we can merge this and the PR for incident timelines! We really need this

finnie2006 · 2022-03-08T18:10:56Z

Its such a nice update, hope he will finally merge this

ckocyigit · 2022-03-28T07:30:49Z

Is it possible to publish an endpoint to pause a specific monitor e.g. via REST.

example: https://kuma/api/pause/<MonitorName>?duration=100"

I think this would really be helpful to solve the issue regarding automated deployments with varying times.

karelkryda · 2022-03-28T12:08:51Z

Is it possible to publish an endpoint to pause a specific monitor e.g. via REST.

example: https://kuma/api/pause/<MonitorName>?duration=100"

I think this would really be helpful to solve the issue regarding automated deployments with varying times.

That sounds like a good idea.

Personally, I would suggest merging this pull request and then making a pull request on it containing API endpoints for maintenance system and incident system.

My point is that now this pull request is in a state where it is ready for deployment. I do not want to unnecessarily prolong the time that will be needed to implement this pull request in the main branch.

acki · 2022-04-26T22:52:59Z

@louislam Please? 😄

Computroniks

Would it be possible to add JSDoc here as well. @karelkryda I know your busy currently with exams so don't worry if you can't do it right now (good luck BTW). If you like, I could lend a hand here, just let me know. I would probably merge from master first though to get all of the comments added from #1499 so we don't end up duplicating.

server/model/maintenance.js

Computroniks · 2022-04-27T21:44:02Z

server/model/maintenance.js

+    }
+
+    /**
+     * Return a object that ready to parse to JSON


Suggested change

* Return a object that ready to parse to JSON

* Return a object that ready to parse to JSON

* @returns {Object}

karelkryda · 2022-04-27T22:21:50Z

Would it be possible to add JSDoc here as well. @karelkryda I know your busy currently with exams so don't worry if you can't do it right now (good luck BTW). If you like, I could lend a hand here, just let me know. I would probably merge from master first though to get all of the comments added from #1499 so we don't end up duplicating.

Yes, it's not a problem. I'm currently wondering if there will also be a need to redo the whole PR because of conflicts.

If it wasn't needed, adding comments is a relatively short-term job and maybe I could do it soon.

Btw. thank you for wishing me luck 😊

gaby · 2022-04-28T00:00:07Z

@karelkryda If I get sometime today or tomorrow, I will submit a PR to your Fork with all the merge conflicts solved. I've done this already for my own copy of uptime-kuma.

karelkryda · 2022-04-28T04:56:46Z

@karelkryda If I get sometime today or tomorrow, I will submit a PR to your Fork with all the merge conflicts solved. I've done this already for my own copy of uptime-kuma.

That sounds great. If I had time on the weekend, I would try to look at it and check the code.

Do you think I should implement the option to choose which page to display maintenance information on?

gaby · 2022-04-28T13:29:42Z

@karelkryda I just submitted a PR in your fork with all the conflicts solved. Once that PR is merge it should make it easier for @louislam to review this PR. 😄

PR is here: karelkryda#3

karelkryda · 2022-04-28T13:43:37Z

@karelkryda I just submitted a PR in your fork with all the conflicts solved. Once that PR is merge it should make it easier for @louislam to review this PR. 😄

PR is here: karelkryda#3

Thanks, it's a lot of code 😅. I'll go through it, test it and prepare for merge.

gaby · 2022-04-28T13:56:28Z

@karelkryda I just submitted a PR in your fork with all the conflicts solved. Once that PR is merge it should make it easier for @louislam to review this PR. 😄
PR is here: karelkryda#3

Thanks, it's a lot of code 😅. I'll go through it, test it and prepare for merge.

I'm not 100% sure if this would help but:

Create a new branch in your fork named: upstream-changes.
I will re-submit the PR against that branch.
Merge the changes from PR into upstream-changes.
Then create a new PR from upstream-changes to master in your fork.

That way the PR will only have the changes related to this PR

# Conflicts: # package-lock.json # server/database.js # server/model/monitor.js # server/routers/api-router.js # server/server.js # src/components/MonitorList.vue # src/components/PingChart.vue # src/icon.js # src/pages/DashboardHome.vue # src/pages/StatusPage.vue # src/router.js # src/util.js

Saibamen

Please fix EFLinx errors and warnings

Saibamen · 2022-04-30T12:47:31Z

server/model/monitor.js

+                }
+                else if (this.type === "http" || this.type === "keyword") {


Suggested change

}

else if (this.type === "http" || this.type === "keyword") {

} else if (this.type === "http" || this.type === "keyword") {

Saibamen · 2022-04-30T12:47:41Z

server/model/monitor.js

+                }
+                else {


Suggested change

}

else {

} else {

Saibamen · 2022-04-30T12:48:02Z

server/model/monitor.js

@@ -903,6 +948,11 @@ class Monitor extends BeanModel {
            monitorID
        ]);
    }
+
+    static async isUnderMaintenance(monitorID) {
+        const maintenance = await R.getRow("SELECT COUNT(*) AS count FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now') AND datetime(maintenance.end_date) >= datetime('now') LIMIT 1", [monitorID]);


Suggested change

const maintenance = await R.getRow("SELECT COUNT(*) AS count FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now') AND datetime(maintenance.end_date) >= datetime('now') LIMIT 1", [monitorID]);

const maintenance = await R.getRow("SELECT COUNT(*) AS count FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now') AND datetime(maintenance.end_date) >= datetime('now') LIMIT 1", [ monitorID ]);

Saibamen · 2022-04-30T12:48:25Z

server/routers/api-router.js

@@ -148,6 +156,30 @@ router.get("/api/status-page/:slug", cache("5 minutes"), async (request, respons
    }

 });
+// TODO: make slug aware


Saibamen · 2022-04-30T12:49:00Z

src/components/MonitorList.vue

+                    <option value="monitor" selected>{{$t('Monitor List')}}</option>
+                    <option value="maintenance">{{$t('Maintenance List')}}</option>


Suggested change

<option value="monitor" selected>{{$t('Monitor List')}}</option>

<option value="maintenance">{{$t('Maintenance List')}}</option>

<option value="monitor" selected>{{ $t('Monitor List') }}</option>

<option value="maintenance">{{ $t('Maintenance List') }}</option>

Saibamen · 2022-04-30T12:49:31Z

src/components/Uptime.vue

@@ -15,6 +15,10 @@ export default {

    computed: {
        uptime() {
+


Suggested change

Saibamen · 2022-04-30T12:49:41Z

src/components/Uptime.vue

@@ -26,6 +30,10 @@ export default {
        },

        color() {
+            if (this.type === "maintenance" || this.monitor.maintenance) {
+                return "maintenance"


Suggested change

return "maintenance"

return "maintenance";

Saibamen · 2022-04-30T12:49:52Z

src/components/Uptime.vue

+            if (this.type === "maintenance" || this.monitor.maintenance) {
+                return "maintenance"
+            }
+


Suggested change

Saibamen · 2022-04-30T12:50:22Z

src/languages/en.js

+    "Pick Affected Monitors...": "Pick Affected Monitors...",
+    "Start of maintenance": "Start of maintenance",
+    "Expected end of maintenance": "Expected end of maintenance",
+    Start: "Start",


Duplicated key

Suggested change

Start: "Start",

Saibamen · 2022-04-30T12:51:24Z

src/mixins/datetime.js

+            if (inputDate.getFullYear() === now.getUTCFullYear() && inputDate.getMonth() === now.getUTCMonth() && inputDate.getDay() === now.getUTCDay())
+                return this.datetimeFormat(value, "HH:mm");
+            else
+                return this.datetimeFormat(value, "YYYY-MM-DD HH:mm");


Suggested change

if (inputDate.getFullYear() === now.getUTCFullYear() && inputDate.getMonth() === now.getUTCMonth() && inputDate.getDay() === now.getUTCDay())

return this.datetimeFormat(value, "HH:mm");

else

return this.datetimeFormat(value, "YYYY-MM-DD HH:mm");

if (inputDate.getFullYear() === now.getUTCFullYear() && inputDate.getMonth() === now.getUTCMonth() && inputDate.getDay() === now.getUTCDay()) {

return this.datetimeFormat(value, "HH:mm");

} else {

return this.datetimeFormat(value, "YYYY-MM-DD HH:mm");

}

Saibamen · 2022-10-12T08:44:44Z

server/database.js

@@ -64,7 +64,7 @@ class Database {
        "patch-add-other-auth.sql": { parents: [ "patch-monitor-basic-auth.sql" ] },
        "patch-add-radius-monitor.sql": true,
        "patch-monitor-add-resend-interval.sql": true,
-        "patch-maintenance-table.sql": true,
+        "patch-maintenance-table2.sql": true,


Please change name (delete 2) before merging into master

# Conflicts: # server/server.js # src/components/settings/General.vue

louislam · 2022-10-15T12:34:17Z

I think it is almost done. I will have a final file changes review on GitHub and quickly release a beta for this. So everyone can test it.

Based on @karelkryda's pull request, I also update followings:

Redesigned and imrpoved UI/UX, put everything under Maintenance Page.
Improved timezone handling, added server side timezone
Besides single time window, I also added 3 recurring types and active/inactive manually.
Update database schema for recurring types

karelkryda · 2022-10-15T12:40:11Z

Thank you @louislam for your cooperation, it looks very good, well done.
I look forward to the release 🎉.

pierreozoux · 2022-10-17T08:26:21Z

Not yet using kuma, but I was waiting this feature to test.

I see all the amazing work you did, and just wanted to say thanks :)

Thanks a lot for this hard work! Have a wonderful day everybody :)

louislam · 2022-10-17T08:30:27Z

Not yet using kuma, but I was waiting this feature to test.

I see all the amazing work you did, and just wanted to say thanks :)

Thanks a lot for this hard work! Have a wonderful day everybody :)

It is available in 1.19.0-beta.0 now, feel free to try.

I would expect it is not fully stable yet, also feel free to submit bug reports.

karelkryda · 2022-10-17T08:42:19Z

Not yet using kuma, but I was waiting this feature to test.

I see all the amazing work you did, and just wanted to say thanks :)

Thanks a lot for this hard work! Have a wonderful day everybody :)

I am glad that this functionality has finally been implemented and I was happy to help with it.
In the end, it's us developers and Uptime Kuma users who have a vested interest in improving open source software like this.

I hope that my next PR related to the incident system (and other PRs) will soon be included in the main branch and I look forward to further excellent cooperation with @louislam.

Have a nice rest of the day

x86dev · 2022-10-17T10:19:06Z

This is awesome news, a big thanks to all who made this possible! Can't wait to test this!

spiezmaestro · 2022-12-11T13:34:01Z

This is the one I have been waiting for! I have weekly reboots on a lot of systems and until now, I'm getting flooded by alert mails. Thanks a lot to all who contributed!!

lachnerd · 2022-12-24T12:18:43Z

Awesome feature, thanks a lot.
Is it possible to make upcoming maintenances visibile on the status pages ?

ex0nuss · 2022-12-24T22:11:24Z

Amazing feature! I have waited for this one sooo long :)
Is it possible to select container by tags? Would be pretty handy this way you can schedule regular maintenances dynamically.

Here a quick example:

I have the tag "autoPatching_weekly_sunday" on some monitors.
Now I schedule a recurring maintenance for every Sunday with the tag "autoPatching_weekly_sunday".
When I add a new monitor, that will be also patched automatically every Sunday, I only need to add the tag ;)

A complete maintenance planning system has been created

0d3414c

Saibamen reviewed Jan 23, 2022

View reviewed changes

minor fixes (missing commas, spaces, translations)

5fda1f0

Saibamen reviewed Jan 23, 2022

View reviewed changes

karelkryda added 2 commits January 24, 2022 22:33

The start and end dates of the maintenance are now stored in UTC, whi…

e7b2832

…ch allows it to be converted between time zones

The SQL query to determine if the monitor is under maintenance is now…

b49e5d5

… in its own method.

douglasparker mentioned this pull request Feb 6, 2022

Scheduled monitoring pause #191

Closed

This was referenced Mar 18, 2022

Global maintenance window where uptime is not monitored? #1384

Closed

Scheduled Down Monitors #1394

Closed

Computroniks suggested changes Apr 27, 2022

View reviewed changes

karelkryda added 2 commits April 30, 2022 13:40

Resolve conflicts

7532acc

Saibamen suggested changes Apr 30, 2022

View reviewed changes

louislam added 5 commits October 11, 2022 01:59

Update Maintenance list order by status

d5c02fc

Merge remote-tracking branch 'origin/master' into maintenance

f6bbd1c

Add info.serverTimezoneOffset and improve some styles

2271ac4

WIP

e07aa98

Update status page's maintenance message

dfb75c8

louislam linked an issue Oct 11, 2022 that may be closed by this pull request

Support timezone in notifications #40

Closed

louislam added 4 commits October 11, 2022 21:48

Update maintenance tables

39b6725

Init dayjs for backend.spec.js

d95e722

Revert testing

7b97660

Revert

8cc3e4b

Saibamen reviewed Oct 12, 2022

View reviewed changes

louislam added 7 commits October 12, 2022 17:02

Implement generateTimeslot() for recurring interval type

2faf866

Add UTC in the serverTimezone dropdown

edacff1

Add index for maintenance tables

aecf958

Merge remote-tracking branch 'origin/master' into maintenance

268cbdb

# Conflicts: # server/server.js # src/components/settings/General.vue

Generate Next Timeslot for recurring interval

0b8d4cd

Implement recurring day of month and day of week

d8a676a

Fix recurring

24cb212

louislam marked this pull request as ready for review October 15, 2022 12:19

Remove unused language keys

6f4424d

louislam merged commit afe12cc into louislam:master Oct 15, 2022

	const { debug, UP, DOWN, PENDING, MAINTENANCE, flipStatus, TimeLogger} = require("../../src/util");
	const { debug, UP, DOWN, PENDING, MAINTENANCE, flipStatus, TimeLogger } = require("../../src/util");

	const { UP, MAINTENANCE, flipStatus, debug} = require("../../src/util");
	const { UP, MAINTENANCE, flipStatus, debug } = require("../../src/util");

	import {getMaintenanceRelativeURL, getMonitorRelativeURL} from "../util.ts";
	import { getMaintenanceRelativeURL, getMonitorRelativeURL } from "../util.ts";

-            }
-        },
+            }
+        },

	* Return a object that ready to parse to JSON
	* Return a object that ready to parse to JSON
	* @returns {Object}

		}
		else if (this.type === "http" \|\| this.type === "keyword") {

	}
	else if (this.type === "http" \|\| this.type === "keyword") {
	} else if (this.type === "http" \|\| this.type === "keyword") {

	const maintenance = await R.getRow("SELECT COUNT(*) AS count FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now') AND datetime(maintenance.end_date) >= datetime('now') LIMIT 1", [monitorID]);
	const maintenance = await R.getRow("SELECT COUNT(*) AS count FROM monitor_maintenance mm JOIN maintenance ON mm.maintenance_id = maintenance.id WHERE mm.monitor_id = ? AND datetime(maintenance.start_date) <= datetime('now') AND datetime(maintenance.end_date) >= datetime('now') LIMIT 1", [ monitorID ]);

		<option value="monitor" selected>{{$t('Monitor List')}}</option>
		<option value="maintenance">{{$t('Maintenance List')}}</option>

A complete maintenance planning system #1213

A complete maintenance planning system #1213

Conversation

karelkryda commented Jan 23, 2022 • edited

Description

Type of change

Checklist

Screenshots (if any)

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

karelkryda commented Jan 28, 2022

Saibamen commented Jan 28, 2022

mathiskir commented Feb 19, 2022 • edited

karelkryda commented Feb 19, 2022

mathiskir commented Feb 19, 2022 • edited

mathiskir commented Feb 19, 2022

nocturn9x commented Mar 1, 2022

finnie2006 commented Mar 8, 2022

ckocyigit commented Mar 28, 2022 • edited

karelkryda commented Mar 28, 2022

acki commented Apr 26, 2022

Computroniks left a comment • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

karelkryda commented Apr 27, 2022

gaby commented Apr 28, 2022

karelkryda commented Apr 28, 2022

gaby commented Apr 28, 2022 • edited

karelkryda commented Apr 28, 2022

gaby commented Apr 28, 2022

Saibamen left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

louislam commented Oct 15, 2022

karelkryda commented Oct 15, 2022

pierreozoux commented Oct 17, 2022

louislam commented Oct 17, 2022

karelkryda commented Oct 17, 2022 • edited

x86dev commented Oct 17, 2022

spiezmaestro commented Dec 11, 2022

lachnerd commented Dec 24, 2022

ex0nuss commented Dec 24, 2022

karelkryda commented Jan 23, 2022 •

edited

mathiskir commented Feb 19, 2022 •

edited

mathiskir commented Feb 19, 2022 •

edited

ckocyigit commented Mar 28, 2022 •

edited

Computroniks left a comment •

edited

gaby commented Apr 28, 2022 •

edited

karelkryda commented Oct 17, 2022 •

edited