{"action":"created","issue":{"url":"https://api.github.com/repos/CachetHQ/Cachet/issues/2044","repository_url":"https://api.github.com/repos/CachetHQ/Cachet","labels_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/2044/labels{/name}","comments_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/2044/comments","events_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/2044/events","html_url":"https://github.com/CachetHQ/Cachet/issues/2044","id":170096653,"number":2044,"title":"Be able to set a component on a maintenance task","user":{"login":"stipx","id":14060217,"avatar_url":"https://avatars.githubusercontent.com/u/14060217?v=3","gravatar_id":"","url":"https://api.github.com/users/stipx","html_url":"https://github.com/stipx","followers_url":"https://api.github.com/users/stipx/followers","following_url":"https://api.github.com/users/stipx/following{/other_user}","gists_url":"https://api.github.com/users/stipx/gists{/gist_id}","starred_url":"https://api.github.com/users/stipx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stipx/subscriptions","organizations_url":"https://api.github.com/users/stipx/orgs","repos_url":"https://api.github.com/users/stipx/repos","events_url":"https://api.github.com/users/stipx/events{/privacy}","received_events_url":"https://api.github.com/users/stipx/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-08-09T07:08:30Z","updated_at":"2016-08-09T07:58:20Z","closed_at":"2016-08-09T07:50:48Z","body":"It would be nice to be able to set the component which is under maintenance on a scheduled maintenance task. \r\n\r\nAnother thing is that a component might have a status \"UNDER MAINTENANCE\" so that it is not titled as major outage or something similar.\r\n\r\nWe're using 2.3.7 right now. "},"comment":{"url":"https://api.github.com/repos/CachetHQ/Cachet/issues/comments/238481121","html_url":"https://github.com/CachetHQ/Cachet/issues/2044#issuecomment-238481121","issue_url":"https://api.github.com/repos/CachetHQ/Cachet/issues/2044","id":238481121,"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":"2016-08-09T07:58:20Z","updated_at":"2016-08-09T07:58:20Z","body":"Sorry, I had a reference to the wrong issue in my clipboard, https://github.com/CachetHQ/Cachet/issues/495 is the right issue (closed now as it's grouped under a different issue).\r\n\r\nIn v3.0.0 we're changing the way that schedules work altogether, so they should be separate entities."}}
{"actor":{"display_login":"jbrooksuk"}}