Updating Incidents Issues

[gonzoinc]

Couple of issues I found when going in and Updating an Incident.

• When you make the update and save, the corresponding screen states:
  Awesome. The incident has been deleted and will not show on your status page.

• if you create an incident and it is initially set to Not notify subscribers, Updates to the incident still send email notifications. No options to disable this in the Update view. Updates should abide by the initial setting or allow the option to not notify subscribers on the update screen.

• Setting an incident to fixed should open the option to allow the service to be set back to Operational. Since you allow the service status option to be available when you create the incident, it should also exist when you resolve the incident.

[jbrooksuk]

What version of Cachet are you using?

[jbrooksuk]

Sorry, obviously it's 2.4 since you're using Incident Updates.

[jbrooksuk]

Issue one is fixed.

[danir-de]

Issue 3 really is something critical in my opinion, since it's not possible to change the state of a service via the api.

[jbrooksuk]

@gonzoinc @chronicals I've started point 2 in #3103

[jbrooksuk]

Thank you for your input on Cachet 2.x. We are shifting our attention and resources to Cachet 3.x and will no longer be supporting the 2.x version. If your feedback or issue is relevant to the 3.x series, we encourage you to engage with the new branch.

For more information on the Cachet rebuild and our plans for 3.x, you can read the announcement here.

We appreciate your understanding and look forward to your contributions to the new version.