Design of Related Issues and Related Merge Requests is inconsistent

Summary

When an issue has both related issues and related merge requests it becomes apparent that the design is inconsistent.

Steps to reproduce

  • Create issue A
  • Create issue B
  • Make B a related issue of A
  • Create merge request C, mention A in its description
  • Look at A

Example Project

https://gitlab.com/jebert1/related-issue-vs-related-mr/issues/1

What is the current bug behavior?

Design is inconsistent

What is the expected correct behavior?

Design is concistent

Relevant logs and/or screenshots

Screen_Shot_2017-07-31_at_12.22.12

Output of checks

This bug happens on GitLab.com