{"action":"created","issue":{"url":"https://api.github.com/repos/cachethq/Cachet/issues/159","labels_url":"https://api.github.com/repos/cachethq/Cachet/issues/159/labels{/name}","comments_url":"https://api.github.com/repos/cachethq/Cachet/issues/159/comments","events_url":"https://api.github.com/repos/cachethq/Cachet/issues/159/events","html_url":"https://github.com/cachethq/Cachet/issues/159","id":53189389,"number":159,"title":"Incident & Component status/mapping","user":{"login":"jaxxstorm","id":1622940,"avatar_url":"https://avatars.githubusercontent.com/u/1622940?v=3","gravatar_id":"","url":"https://api.github.com/users/jaxxstorm","html_url":"https://github.com/jaxxstorm","followers_url":"https://api.github.com/users/jaxxstorm/followers","following_url":"https://api.github.com/users/jaxxstorm/following{/other_user}","gists_url":"https://api.github.com/users/jaxxstorm/gists{/gist_id}","starred_url":"https://api.github.com/users/jaxxstorm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaxxstorm/subscriptions","organizations_url":"https://api.github.com/users/jaxxstorm/orgs","repos_url":"https://api.github.com/users/jaxxstorm/repos","events_url":"https://api.github.com/users/jaxxstorm/events{/privacy}","received_events_url":"https://api.github.com/users/jaxxstorm/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/cachethq/Cachet/labels/discussion","name":"discussion","color":"DB0A5B"},{"url":"https://api.github.com/repos/cachethq/Cachet/labels/enhancement","name":"enhancement","color":"4B77BE"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2014-12-31T15:48:12Z","updated_at":"2015-01-06T16:05:24Z","closed_at":"2015-01-06T16:05:24Z","body":"After a discussion in gitter, I'd like to propose a change to the incidents status field in order to better map to the component status.\r\n\r\nAt the moment, components have an \"operational status\" which determine whether the component is working as expected or is experiencing issues. The thing I've noticed is when you update the \"operational status\" of an incident, it doesn't update the banner on the dashboard saying \"everything is okay\"\r\n\r\nIncidents also have a \"status\", but the status is the same field name (in the API at least) but it denotes a different TYPE of status, mainly the progress of the fix.\r\n\r\nI would like to propose:\r\n\r\n- Changing the current incident status field to something like \"progress_status\", whereby the progress of resolving the incident is detailed\r\n- Changing the \"status\" of the incident to be the same as the component status.\r\n\r\nThat way, when an incident happens, you should be able to select a component that the status affects (as well as leaving it blank, if required) and when the incident is created, it also updates the status of the component, all the way through to resolution."},"comment":{"url":"https://api.github.com/repos/cachethq/Cachet/issues/comments/68885377","html_url":"https://github.com/cachethq/Cachet/issues/159#issuecomment-68885377","issue_url":"https://api.github.com/repos/cachethq/Cachet/issues/159","id":68885377,"user":{"login":"jbrooksuk","id":246103,"avatar_url":"https://avatars.githubusercontent.com/u/246103?v=3","gravatar_id":"","url":"https://api.github.com/users/jbrooksuk","html_url":"https://github.com/jbrooksuk","followers_url":"https://api.github.com/users/jbrooksuk/followers","following_url":"https://api.github.com/users/jbrooksuk/following{/other_user}","gists_url":"https://api.github.com/users/jbrooksuk/gists{/gist_id}","starred_url":"https://api.github.com/users/jbrooksuk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbrooksuk/subscriptions","organizations_url":"https://api.github.com/users/jbrooksuk/orgs","repos_url":"https://api.github.com/users/jbrooksuk/repos","events_url":"https://api.github.com/users/jbrooksuk/events{/privacy}","received_events_url":"https://api.github.com/users/jbrooksuk/received_events","type":"User","site_admin":false},"created_at":"2015-01-06T16:05:24Z","updated_at":"2015-01-06T16:05:24Z","body":"@jaxxstorm nope, not yet, but we could supply a `component_status` value in the API to update it.\r\n\r\nI'm actually going to close this issue; [see why here](https://github.com/cachethq/Cachet/pull/301#issuecomment-68881901). In the incident panel, you'll be able to pick the component then change its status inline (on POST)."}}