That's exactly why the "GitHub" and "J! Issue" buttons are on the list view. You're taken directly to the relevant item on those two sites.

I'm not adding code to pull the entire issue thread when fetching data. The number of API requests to pull that off is too many and in general if it causes things to stop working with anonymous API requests I'm not doing it.

Loved the phrase "I'm not doing it." ?

I understand its a waste calling apis for more details. However, the actual list api call which get you the list of pulls returns the initial comment and more other relevant details already. Can't we use it for quick lookup within the component? For more information user always has a choice to go relevant pages.

The first couple hundred characters of the issue's description are used as a tooltip on the issue's title. Issue is it's still in markdown format (because it would need added API calls to convert it to HTML or inclusion of a PHP markdown library to parse it into plain text), so with the standardized template it's not useful at all anymore.

I hesitate to make it something that can display inline because some of the issue bodies get excessively long, especially when folks copy/paste the output from the sys info text file into the issue instead of adding it as a file attachment. Plus, again rendering it means doing something to convert the markdown into a human readable format.

Ya, it's a little slow to click a button and go to a third party website, but all of the issue context can be found there. And to me that's still a better option than giving a small snippet of data in the component which may not have all the needed information to do anything with an issue.