There is an interesting point re: how we deal with PRs. If a PR in Github is just an issue coming from the planning interface, then in my case I may have information for a single issue coming from two sources that needs to be aggregated in some way. 

If we treat a PR just as additional "decoration" for a feature (as we can do with branches and jobs) then it can be dealt with at the next stage, when we add info to a feature.