{"action":"opened","issue":{"url":"https://api.github.com/repos/FSInvestments/ListManagement/issues/9","repository_url":"https://api.github.com/repos/FSInvestments/ListManagement","labels_url":"https://api.github.com/repos/FSInvestments/ListManagement/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/FSInvestments/ListManagement/issues/9/comments","events_url":"https://api.github.com/repos/FSInvestments/ListManagement/issues/9/events","html_url":"https://github.com/FSInvestments/ListManagement/issues/9","id":157765733,"number":9,"title":"Updated_Rep_Lists: AccountID assignment for found contacts","user":{"login":"rickyschoolsFS","id":19492730,"avatar_url":"https://avatars.githubusercontent.com/u/19492730?v=3","gravatar_id":"","url":"https://api.github.com/users/rickyschoolsFS","html_url":"https://github.com/rickyschoolsFS","followers_url":"https://api.github.com/users/rickyschoolsFS/followers","following_url":"https://api.github.com/users/rickyschoolsFS/following{/other_user}","gists_url":"https://api.github.com/users/rickyschoolsFS/gists{/gist_id}","starred_url":"https://api.github.com/users/rickyschoolsFS/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rickyschoolsFS/subscriptions","organizations_url":"https://api.github.com/users/rickyschoolsFS/orgs","repos_url":"https://api.github.com/users/rickyschoolsFS/repos","events_url":"https://api.github.com/users/rickyschoolsFS/events{/privacy}","received_events_url":"https://api.github.com/users/rickyschoolsFS/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-31T20:42:26Z","updated_at":"2016-05-31T20:42:26Z","closed_at":null,"body":"Currently, the SFDC searches pull in the AccountID that is currently assigned to the contact (if found). While it is great to know what the records current accountID is, we need to make sure to assign the contact a new accountID. There could be a few additional caveats to consider when building out fix for this bug:\r\n\r\n**Considerations & Corner-cases**\r\n- The list received could be 'older' than another rep list that we received. In these cases we would need: 1) a way to identify when the list is as of and 2) identify when the current BD that the advisor is assigned to was last updated.\r\n\r\n@iammaxc "}}
{"actor":{"display_login":"rickyschoolsFS"}}