Skip to content

Schedule Updates #107

@jbrooksuk

Description

@jbrooksuk

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions