I just noticed that when I created a new issue in a repository in our local GitLab instance that I monitor with GitLight, it showed a merge request of the same ID instead (the merge request got closed a longer time ago, and I was first wondering why it suddenly shows up again, until I realized that it had the same ID as the issue). In GitLab, issues and MRs have separate ID spaces (as opposed to GitHub), my guess is that there is some code in GitLight that doesn't really know it, or has an implicit expectation that there are more issues than MRs in a repository.
I just noticed that when I created a new issue in a repository in our local GitLab instance that I monitor with GitLight, it showed a merge request of the same ID instead (the merge request got closed a longer time ago, and I was first wondering why it suddenly shows up again, until I realized that it had the same ID as the issue). In GitLab, issues and MRs have separate ID spaces (as opposed to GitHub), my guess is that there is some code in GitLight that doesn't really know it, or has an implicit expectation that there are more issues than MRs in a repository.