Comments on the Scheduled maintenance feature in 0.2.1

[weeblr]

Feature request

I finally managed to update to 0.2.1 (had to force the version on npm) and added a couple of scheduled maintenance items for testing. I have the following comments:

• I confirm that this is a feature request rather than a question.

How should this be implemented in your opinion?

1 - Adding a scheduled maintenance item is quick and simple, good work
2 - As previously mentioned, I'd rather have the "Scheduled maintenance" section displayed above the current status section. Reason is simple: as soon as you have more than a few systems listed, the "Scheduled maintenance" section requires scrolling and will be missed by many

3 - The Date/Time at which the Scheduled maintenance will happen is not visible enough. It should be made very large/visible, at least as much as the maintenance title
4 - I added some text to the event but that text is not visible anywhere:

---
title: Server upgrade
date: '2018-12-13T14:34:46.338Z'
scheduled: '2018-12-15T12:00:00.000Z'
duration: 30
severity: under-maintenance
affectedsystems:
  - site
  - helpdesk
  - documentation
resolved: false
---

Our hosting company has required that our main server is rebooted for software updates.

::: update under-maintenance | 2018-12-13T14:45:46.338Z
We have been informed that the expected duration of the maintenance is now 60mn.
:::

<!--- language code: en -->

The text "Our hosting company..." and the update text are not visible anywhere. You can't even click through to get to the details of the event like on regular incidents - although I would not want that either, that's not very handy. See point #5 below

5 - I would suggest each incident, whether standard or scheduled maintenance, displays the title, then the first 2or 3 lines of description and then a button can be clicked to expand in place (don't go to another page) to view the full text content of the incident including description and any subsequent update.

Looking forward to your comments, thanks for the update.

Best regards

Are you willing to work on this yourself?**

[juliomrqz]

Hello, @weeblr. Sorry for the late response. We also agree the style of the Scheduled Maintenance can be improved. Currently, it's displayed only the description of that "special" incident. When we have an agreement on this issue we will let you know.

[weeblr]

Hi @juliomrqz

Currently, it's displayed only the description of that "special" incident.

The key points really are: a/ the date/time should be the most visible part and b/ don't send people to another page to view details of the event. There's not much text to be displayed, just have an expandable section.

We cannot switch to Statusfy yet because of those UI concerns (from Cachet) but I look forward to further enhancements.

Best regards

[weeblr]

Commenting to keep open.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[weeblr]

Commenting to keep open.

[giovagnoli]

Hello @weeblr. We're working on this issue. It will be included in the next release.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[weeblr]

Commenting to keep open.

[juliomrqz]

Commenting to keep open.

[juliomrqz]

Hello, @weeblr. How are you doing?

We consider most of your suggestions, and they will be available in the next stable version, but in the meantime, you can test them using the version 0.3.0-beta.1.

This is what we change:

• The end date of the Scheduled Maintenance is now displayed.
• The Date of all incidents is now bigger and bolder.
• The content of the Scheduled Maintenance is displayed instead of the description.
• You can define the position of Scheduled Maintenance Section. Check the available options.

Let me know if you have any question or suggestion.

Finally, I invite you to leave your comment in the Statusfy Users issue when you start using Statusfy in your company or organization 🤓.

[weeblr]

Hi @juliomrqz

Doing well, thanks. I give it a shot and can comment as follow:

1. Could not make statusfy to work on windows:

npm ERR! code ELIFECYCLE
npm ERR! errno 3221225725

Quickly googled it and saw other projects mentioning this but could not do anything of what I read.

2 - I then ran through the standard pipeline on our Gitlab instance and that worked better. I noticed the following:

• cool to be able to change scheduled maintenance position,

• my only remark on the scheduled maintenance display is that I would drop the dimmed "created at " date at the bottom of the scheduled incident. Does not bring any value.

• My logo image is not showing. I believe it's because the status page is in a subfolder, as is common with Gitlab. The src of the logo image is /static/image/xxxxxx.png and that fails when the site is in a subfolder

• Likewise, the Incidents History link is wrong, it misses the subfolder and assumes a naked domain.

Note that I have proper baseUrl set in the config file (I tried both with and without a trailing slash after the URL).

Cheers

[weeblr]

Hi again

As this issue is closed and this part is another topic, I opened a separate issue: #163