Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Planned Maintenance Use Case: notice posts showing up with future date #205

Closed
Wimmetje opened this issue Sep 7, 2021 · 5 comments
Closed

Comments

@Wimmetje
Copy link

Wimmetje commented Sep 7, 2021

Is your feature request related to a problem? Please describe.
When I create a issue with a future date, the announcement shows up for the future date, but the status of the servers go to maintenance mode.

Describe the solution you'd like
When filled in with a future date, the server status has to be on operational until the date that the maintenance mode is active.

Describe alternatives you've considered
I tried to make the issue resolved until the maintenance date, but that would show the issue up as resolved, when that is not the case, the maintenance has to take place yet.

@mistermantas
Copy link
Member

Hm. Try informational posts. Although I haven't thought about this fully yet, thanks for posting

@Wimmetje
Copy link
Author

Wimmetje commented Sep 8, 2021

When you set the issue as a post instead of a issue, the notice doesn't appear on top of the site, and it will not show up in the incident history

@Wimmetje
Copy link
Author

Maybe you could make that when it's a notice post, the announcement will still appear

@Wimmetje
Copy link
Author

It would be really nice if this could also be included in the hacktoberfest update

@mistermantas mistermantas changed the title Planned Maintenance Planned Maintenance Use Case: notice posts showing up with future date Oct 2, 2021
@mistermantas
Copy link
Member

Hey again,

When I create a issue with a future date, the announcement shows up for the future date, but the status of the servers go to maintenance mode.

When an issue is NOT resolved, it alters the overall status of the site. In other words, it doesn't matter what the date is. To not alter the overall status of the site or component, you would have to set it as resolved.

I see the problem here though - that's kind of dumb if you're planning for future maintenance.

When filled in with a future date, the server status has to be on operational until the date that the maintenance mode is active.

That's not possible because the server would have to re-trigger a new deploy at a certain time which, to my knowledge, is not possible with a fully static site.

You could hack something with JS together but that would break the API and other things.

Status changes are always manual.

I tried to make the issue resolved until the maintenance date, but that would show the issue up as resolved, when that is not the case, the maintenance has to take place yet.

Yep, this is the real issue here and I think informational posts don't quite accomplish what they're supposed to.

Proposed solution

  1. When planned maintenance is upcoming, you should be able to create an informational post that can be 'pinned' or change the status in a non destructive way, i.e. "Maintenance happening soon"
  2. When the maintenance has to begin, just create (or change around the existing post) so it can become an issue.
  3. Then set it as resolved.

Future dates are really hard to work with for this project because I prioritised reliability over features but I think you can accomplish what you want when I update informational posts to showcase this better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants