gitlab-roadmap.md

@@ -123,8 +123,6 @@ but also:
 
 ## How one would search to find if an encountered problem was a known issue, an issue being addressed, etc.?
 
-Main issue: #823
-
 > "It would really help if a non-developer, non Github user could get some sense of how to use the proposed repository and, specifically, how one would search to find if an encountered problem was a known issue, an issue being addressed, etc." (@dtarrant)
 
 The proposed Gitlab structure would be to have project spaces around components/themes of CiviCRM (financial, cloud-native, translation, reports, etc, but there would still be a "core" project).
@@ -135,6 +133,8 @@ It might also be necessary to also search the pull-request queue on Github, in c
 
 ## Splitting issues across projects might be confusing? Triage?
 
+Main issue: #823
+
 > "We cannot expect our users to have to understand the internal workings of CiviCRM in order to choose where they need to file their bug report." (@cividesk/Nicolas)
 
 > "Note that if easy to move issues around projects in GitLab, we might resolve end-user reporting of issues through an external, non-authenticated form collecting basic info on the issue (and reporter), which would then create an issue in the 'triage' project in GitLab. The issue would then be triaged and moved to the appropriate development project by technical contributors." (@cividesk/Nicolas)