We were loading board issues twice, because we invalidated the
issues scope after loading them by adding another `preload`,
so the query fired again during template rendering.
By eager-loading issues upfront, we can enforce this to always be
just one query.