{"action":"created","issue":{"url":"https://api.github.com/repos/Shippable/support/issues/1967","labels_url":"https://api.github.com/repos/Shippable/support/issues/1967/labels{/name}","comments_url":"https://api.github.com/repos/Shippable/support/issues/1967/comments","events_url":"https://api.github.com/repos/Shippable/support/issues/1967/events","html_url":"https://github.com/Shippable/support/issues/1967","id":112973257,"number":1967,"title":"We no longer have access to the subscription data on the UI","user":{"login":"pquentin","id":42327,"avatar_url":"https://avatars.githubusercontent.com/u/42327?v=3","gravatar_id":"","url":"https://api.github.com/users/pquentin","html_url":"https://github.com/pquentin","followers_url":"https://api.github.com/users/pquentin/followers","following_url":"https://api.github.com/users/pquentin/following{/other_user}","gists_url":"https://api.github.com/users/pquentin/gists{/gist_id}","starred_url":"https://api.github.com/users/pquentin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pquentin/subscriptions","organizations_url":"https://api.github.com/users/pquentin/orgs","repos_url":"https://api.github.com/users/pquentin/repos","events_url":"https://api.github.com/users/pquentin/events{/privacy}","received_events_url":"https://api.github.com/users/pquentin/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-10-23T08:15:55Z","updated_at":"2015-10-23T11:04:01Z","closed_at":null,"body":"We no longer have access to our data in the Shippable UI. However, **builds still run when we push commits on bitbucket**.\r\n\r\n### Home page\r\nOn https://app.shippable.com/, I see \"No builds have been triggered yet.\" and there is no mention of our team.\r\n\r\n### Subscription page\r\nWhen I go to https://app.shippable.com/subscriptions/547c792bd46935d5fbbf0b11 as pquentin (signed in from bitbucket), I get \"You don't have sufficient permissions to perform this operation\" in a red alert box. (And the spinner never stops.)\r\n\r\n### Build page\r\nWhen I go to a specific build, eg. https://app.shippable.com/builds/5629cbf3954d220c00b56fab, I get the following message in the red alert box:\r\n\r\n    {\r\n      \"id\":1004,\r\n      \"message\":\"GET failed for subscriptionId :547c792bd46935d5fbbf0b11\",\r\n      \"methodName\":\"caller:54f477fa5ab6cc1352906167|projects|chkPermForId:54c8b9d15ab6cc13528a0671|_getSubPermBySubId\",\r\n      \"link\":401\r\n    }\r\n\r\nThe page itself displays \"Build not found\".\r\n\r\nWhat's going on? Thanks!"},"comment":{"url":"https://api.github.com/repos/Shippable/support/issues/comments/150544370","html_url":"https://github.com/Shippable/support/issues/1967#issuecomment-150544370","issue_url":"https://api.github.com/repos/Shippable/support/issues/1967","id":150544370,"user":{"login":"rageshkrishna","id":1134972,"avatar_url":"https://avatars.githubusercontent.com/u/1134972?v=3","gravatar_id":"","url":"https://api.github.com/users/rageshkrishna","html_url":"https://github.com/rageshkrishna","followers_url":"https://api.github.com/users/rageshkrishna/followers","following_url":"https://api.github.com/users/rageshkrishna/following{/other_user}","gists_url":"https://api.github.com/users/rageshkrishna/gists{/gist_id}","starred_url":"https://api.github.com/users/rageshkrishna/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rageshkrishna/subscriptions","organizations_url":"https://api.github.com/users/rageshkrishna/orgs","repos_url":"https://api.github.com/users/rageshkrishna/repos","events_url":"https://api.github.com/users/rageshkrishna/events{/privacy}","received_events_url":"https://api.github.com/users/rageshkrishna/received_events","type":"User","site_admin":false},"created_at":"2015-10-23T11:04:01Z","updated_at":"2015-10-23T11:04:01Z","body":"@pquentin You're absolutely right.\r\n\r\nWe regularly purge old permissions to make sure that when you remove collaborators from your projects, they also lose access to those projects on Shippable. Unfortunately, a bug in our sync routine allowed the purge to happen even though we were not able to get any new permissions from BitBucket. We're working on fixing this."}}