Comment by bsuvc
3 days ago
> loading a cross repo issue is a much slower experience
Why not solve the real problem instead of putting in a janky workaround?
At risk of being cliche, it seems like you guys could benefit from the 5 Whys approach here: "Why is loading a cross repo issue slow?" and iterate until you discover the root cause, and fix that.
I suspect fixing the root cause is going to be a lot less glorious career-wise than implementing a UX change that is easier to tout at review time (well maybe not so much after this debacle).
Maybe fixing the root cause is slower, and this janky workaround was quicker as its something largely already built (a few views/links in Github already open issues in a drawer).
You've never done a temporary fix to stop the bleeding?