{"action":"created","issue":{"url":"https://api.github.com/repos/coderly/process/issues/35","labels_url":"https://api.github.com/repos/coderly/process/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/coderly/process/issues/35/comments","events_url":"https://api.github.com/repos/coderly/process/issues/35/events","html_url":"https://github.com/coderly/process/issues/35","id":62545535,"number":35,"title":"PRs related to more than one task.","user":{"login":"idelahoz","id":777019,"avatar_url":"https://avatars.githubusercontent.com/u/777019?v=3","gravatar_id":"","url":"https://api.github.com/users/idelahoz","html_url":"https://github.com/idelahoz","followers_url":"https://api.github.com/users/idelahoz/followers","following_url":"https://api.github.com/users/idelahoz/following{/other_user}","gists_url":"https://api.github.com/users/idelahoz/gists{/gist_id}","starred_url":"https://api.github.com/users/idelahoz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/idelahoz/subscriptions","organizations_url":"https://api.github.com/users/idelahoz/orgs","repos_url":"https://api.github.com/users/idelahoz/repos","events_url":"https://api.github.com/users/idelahoz/events{/privacy}","received_events_url":"https://api.github.com/users/idelahoz/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/coderly/process/labels/high%20priority","name":"high priority","color":"eb6420"},{"url":"https://api.github.com/repos/coderly/process/labels/RFC","name":"RFC","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-17T23:56:13Z","updated_at":"2015-03-18T17:16:01Z","closed_at":null,"body":"# the problem.\r\nWhen developing a large feature, that's made by several tasks, sometimes the code for each task is so coupled that it makes sense to keep everything into a single PR.\r\n\r\nThe main issue with this is task labeling, if I mark a task as \"awaiting review\", someone clicks on the PR link, and the PR is at \"needs work\"(cause its not fully done yet), its inconsistent.\r\n\r\nHow should we deal with this case?"},"comment":{"url":"https://api.github.com/repos/coderly/process/issues/comments/83064234","html_url":"https://github.com/coderly/process/issues/35#issuecomment-83064234","issue_url":"https://api.github.com/repos/coderly/process/issues/35","id":83064234,"user":{"login":"JoshSmith","id":321667,"avatar_url":"https://avatars.githubusercontent.com/u/321667?v=3","gravatar_id":"","url":"https://api.github.com/users/JoshSmith","html_url":"https://github.com/JoshSmith","followers_url":"https://api.github.com/users/JoshSmith/followers","following_url":"https://api.github.com/users/JoshSmith/following{/other_user}","gists_url":"https://api.github.com/users/JoshSmith/gists{/gist_id}","starred_url":"https://api.github.com/users/JoshSmith/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JoshSmith/subscriptions","organizations_url":"https://api.github.com/users/JoshSmith/orgs","repos_url":"https://api.github.com/users/JoshSmith/repos","events_url":"https://api.github.com/users/JoshSmith/events{/privacy}","received_events_url":"https://api.github.com/users/JoshSmith/received_events","type":"User","site_admin":false},"created_at":"2015-03-18T17:16:01Z","updated_at":"2015-03-18T17:16:01Z","body":"I actually have a proposal for this.\r\n\r\nIf you have a large PR that has multiple tasks related to it, and you want the specific piece that you worked on to be reviewed, I think you should:\r\n\r\n- Add a comment to the PR summarizing what you did\r\n- Link to that comment in the Asana task you're going to mark as `awaiting review`\r\n- Now when you click that link, you don't really care what the label of the PR itself is. It could be `blocked` for all you care, but you now have a place to review and comment on the task at hand.\r\n\r\nWhat do you think @idelahoz and @venkatd?"}}