{"action":"opened","issue":{"url":"https://api.github.com/repos/pivotaltracker/trissues/issues/35","labels_url":"https://api.github.com/repos/pivotaltracker/trissues/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/pivotaltracker/trissues/issues/35/comments","events_url":"https://api.github.com/repos/pivotaltracker/trissues/issues/35/events","html_url":"https://github.com/pivotaltracker/trissues/issues/35","id":71606381,"number":35,"title":"When a Story is accepted in Tracker, mark the linked GitHub Issue closed","user":{"login":"gleneivey","id":57512,"avatar_url":"https://avatars.githubusercontent.com/u/57512?v=3","gravatar_id":"","url":"https://api.github.com/users/gleneivey","html_url":"https://github.com/gleneivey","followers_url":"https://api.github.com/users/gleneivey/followers","following_url":"https://api.github.com/users/gleneivey/following{/other_user}","gists_url":"https://api.github.com/users/gleneivey/gists{/gist_id}","starred_url":"https://api.github.com/users/gleneivey/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gleneivey/subscriptions","organizations_url":"https://api.github.com/users/gleneivey/orgs","repos_url":"https://api.github.com/users/gleneivey/repos","events_url":"https://api.github.com/users/gleneivey/events{/privacy}","received_events_url":"https://api.github.com/users/gleneivey/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-28T14:31:28Z","updated_at":"2015-04-28T14:31:28Z","closed_at":null,"body":"This should probably be enabled in the configuration, or perhaps the feature is to have a configuration variable the sets the Tracker story state, entry to which causes the GitHub Issue to be closed.  (Different Tracker workflows might use the finished and delivered states differently than the Tracker team, making them more appropriate triggers for closing the issues.)\r\n\r\nConsider writing a story for the reverse--are there actions that can be performed on a GitHub Issue (say merging the code from an Issue that is a pull request) which TRIssues should use as triggers for story state changes in Tracker (merging a pull request could Finish the Issue's story)?\r\n"}}