summaryrefslogtreecommitdiffstats
path: root/wiki/src/blueprint/GitLab.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/src/blueprint/GitLab.mdwn')
-rw-r--r--wiki/src/blueprint/GitLab.mdwn10
1 files changed, 8 insertions, 2 deletions
diff --git a/wiki/src/blueprint/GitLab.mdwn b/wiki/src/blueprint/GitLab.mdwn
index 0090f4b..1b14685 100644
--- a/wiki/src/blueprint/GitLab.mdwn
+++ b/wiki/src/blueprint/GitLab.mdwn
@@ -327,12 +327,13 @@ Tails community.
* Preserve issue status:
+ - "New" → open
- "Confirmed" → open, "1. To do" label
- "In Progress" → open, "2. Doing" label
- "Needs Validation" → open, "3. Needs Validation" label
- - "New" → open
- "Duplicates" → closed, "Duplicate" label
- "Rejected" → closed, "Rejected" label
+ - "Resolved" → closed
* Preserve "Target version" → Milestone
@@ -385,7 +386,7 @@ Tails community.
It looks like GitLab does not support private comments.
-* Issue assignee
+* Preserve issue assignee
It is acceptable to require assignees to manually create their
GitLab user account themselves before the final migration.
@@ -401,6 +402,10 @@ Tails community.
- _Help Desk_: recently created, not used yet
- _Sysadmins_: 15 tickets as of 2019-11-18
+* Preserve the value of the _Blueprint_ custom field
+
+ Adding this information to the issue description is good enough.
+
### SHOULD
* Convert more Textile issue description and comments to Markdown
@@ -422,6 +427,7 @@ Tails community.
See "Other issues metadata" section above for some discussion about why.
* Log time
+* Start date
* Due date
* Tracker
* % Done