{"action":"opened","issue":{"url":"https://api.github.com/repos/OSSIA/i-score/issues/345","repository_url":"https://api.github.com/repos/OSSIA/i-score","labels_url":"https://api.github.com/repos/OSSIA/i-score/issues/345/labels{/name}","comments_url":"https://api.github.com/repos/OSSIA/i-score/issues/345/comments","events_url":"https://api.github.com/repos/OSSIA/i-score/issues/345/events","html_url":"https://github.com/OSSIA/i-score/issues/345","id":196148986,"number":345,"title":"[feature-request] up for debate : negative trigger","user":{"login":"pchdev","id":9993105,"avatar_url":"https://avatars.githubusercontent.com/u/9993105?v=3","gravatar_id":"","url":"https://api.github.com/users/pchdev","html_url":"https://github.com/pchdev","followers_url":"https://api.github.com/users/pchdev/followers","following_url":"https://api.github.com/users/pchdev/following{/other_user}","gists_url":"https://api.github.com/users/pchdev/gists{/gist_id}","starred_url":"https://api.github.com/users/pchdev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pchdev/subscriptions","organizations_url":"https://api.github.com/users/pchdev/orgs","repos_url":"https://api.github.com/users/pchdev/repos","events_url":"https://api.github.com/users/pchdev/events{/privacy}","received_events_url":"https://api.github.com/users/pchdev/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-16T20:36:02Z","updated_at":"2016-12-16T20:36:02Z","closed_at":null,"body":"this is one of the things we've mentioned this week: if the max duration has been reached (and if there is in fact one), cancel the state execution, but continue the time progression from the same cancelled state. \r\n\r\nin a practical point of view: the user has a “time-window“ available to trigger something, if he misses it, nothing happens, time progression continues. "}}
{"actor":{"display_login":"pchdev"}}