|author||intrigeri <email@example.com>||2019-11-18 15:14:45 +0000|
|committer||intrigeri <firstname.lastname@example.org>||2019-11-18 15:14:45 +0000|
GitLab: more metadata
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
1 files changed, 21 insertions, 1 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 9c301f6..ad777ca 100644
@@ -382,6 +382,22 @@ Tails community.
It looks like GitLab does not support private comments.
+* Issue assignee
+ It is acceptable to require assignees to manually create their
+ GitLab user account themselves before the final migration.
+* Existing issues assigned to a group must remain trackable, somehow.
+ This feature is not intensively used. We can leave it up to the
+ teams who use it to decide how they want to track these tickets on
+ GitLab. A temporary label to not lose track of these tickets would
+ be good enough as far as the migration is concerned.
+ We have two such groups:
+ - _Help Desk_: recently created, not used yet
+ - _Sysadmins_: 15 tickets as of 2019-11-18
* Convert more Textile issue description and comments to Markdown
@@ -417,7 +433,11 @@ Relevant features — to be triaged as MUST/SHOULD/MAY:
* Issue notes that only change metadata.
* Does not require global GitLab administration token.
* Does not require SSH access to the GitLab machine.
-* User groups
+* Which user:
+ - created an issue
+ - wrote a note
+ - modified the metadata of an issue
+* Existing user accounts