HN user
Yes, pretty much this as well as some additional complexities due to the issue content being in React and the header in Rails - to the cost of approx 500-800ms p50 for a page load vs sub 100ms for a nav to an issue in the same repo (or without the header which is what we tried with this change here)
This was a performance driven change. We added this as loading a cross repo issue is a much slower experience than loading an issue in the same repo due to the way the header is loaded (which is being worked on).
But we hear you on the feedback - we will roll this back while we keep pushing on the root performance causes.
[update - this change has been reverted and the previous behaviour is back]
Have you checked out any of the GitHub plugins that do this, something like https://www.zenhub.io could help you add more structure to GitHub
If you use GitHub, then ZenHub is a great option. It is a Chrome extension which adds project management functionality inside the GitHub interface.
Disclosure: I work at ZenHub - the favourite feedback I get is how much it cuts down on context switching between where developers want to live - GitHub, and where Project Managers want to live Jira/Trello/etc, as everyone can work directly from GitHub Issues.