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

Schedule Updates #107

Open
jbrooksuk opened this issue Oct 11, 2024 · 0 comments · May be fixed by #109
Open

Schedule Updates #107

jbrooksuk opened this issue Oct 11, 2024 · 0 comments · May be fixed by #109
Labels
enhancement New feature or request hacktoberfest
Milestone

Comments

@jbrooksuk
Copy link
Member

While maintaining production status pages, one issue I often run into is that we will schedule maintenance, something will go wrong or is delayed and I need to update users. I'm not a fan of editing the schedule itself, since that's not representative of what the actual maintenance was for.

In Cachet, incidents can already have multiple updates via the incident_updates table. I think this table should be renamed to updates and become a polymorphic relation for incidents and schedules.

Things that need updating:

  • Database Migrations - rename incident_updates to updates, add morphable columns, migrate existing updates into a polymorphic structure for incidents.
  • Status Page - let's show that a schedule has x updates.
  • Actions - we'll need to refactor how the updates are handled, probably in the form of a CreateUpdate action that takes a model and stores an update on it.
  • API - we'll need to update how updates are handled.
  • Dashboard - so that IncidentUpdateResource becomes UpdateResource and can be attached to the incident and schedule resources.

I think the trickiest part of this will be ensuring that upgrades from 2.x to 3.x work fine, but I intend on doing that bit of work nearer to the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant