Consistent design for epic issues list and related issues list

In https://gitlab.com/gitlab-org/gitlab-ee/issues/3551#note_46493460 it was proposed to reuse the Related Issues component for Epic issues list. This keeps the UI consistent, and reduces both work required and duplicated code.

Here's the original proposal:

Epic Issue
Screen_Shot_2017-11-08_at_11.19.50_pm_copy Screen_Shot_2017-11-08_at_11.24.11_pm_copy

This design seems to increase the vertical space unnecessarily and introduces some concerns about how the length of project+issue IDs look and behave differently on related issues vs epic issues:

  • Related issues: we can generalize about related issues being mainly used inside of a single project (even though it's possible to have related issues from other projects), so these usually have shorter issue reference because it's only an issue ID
  • Epic issues: these have longer issue references because issue IDs prefixed with one or more project/group references