always use cross-project reference when automatically insert reference

Description

When working with many groups, forks and merges between projects on the same GitLab instance, is quite common that the same short reference (e.g. issue #1 or merge request !2) is used in different project/group. This is an issue because #1 has a meaning in a given project, while it has a completely different one on another project. When a commit/mr/whatever-item has this reference and is be used on both of them (e.g. due merge or cherry-pick), this lead to missing information or, even worst, misleading information.

Proposal

I resolve this kind of issue by always use full-cross-project reference (group/project#1 instead of #1) when manually entering reference (e.g. on commit messages This closes group/project#1) but it quite annoying when using feature like merge request on a branch that has been created from an issue (which just reference automatically to #1)

Would it be possible to always use cross-project reference? or, at least, make this configurable?

Links / references

Nothing for now, sorry 😉