Commit b3758aba authored by 127.0.0.1's avatar 127.0.0.1 Committed by IkiWiki
Browse files

This reverts commit bd7c7249

parent 800b50d7
......@@ -520,9 +520,7 @@ Tails community.
Examples:
- private issue: [[!tails_ticket 10346]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/10346>
- public issue moved to another project: [[!tails_ticket 6033]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/6033>
* Preserve parent/subtask relationship in a way that GitLab will
enforce, i.e. prevent closing the GitLab issue corresponding to the
......@@ -530,8 +528,6 @@ Tails community.
not completed.
Examples: [[!tails_ticket 15878]], [[!tails_ticket 12213]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/15878>,
<https://gitlab.tails.boum.org/tails/tails/-/issues/12213>
Implementation idea: a GitLab issue imported from a Redmine issue
that has subtasks could have a list of tasks (checklist), with each
......@@ -548,8 +544,6 @@ Tails community.
see the "Core team (self-)management" section.
Examples: [[!tails_ticket 15878]], [[!tails_ticket 12213]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/15878>,
<https://gitlab.tails.boum.org/tails/tails/-/issues/12213>
Implementation idea: add the "X blocks Y" information in the
description of issues X and Y and/or as comments on X and Y.
......@@ -571,7 +565,6 @@ Tails community.
Adding this information as-is in a comment would be good enough.
Example: [[!tails_ticket 16173]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/16173>
* Preserve Category, Affected Tool, Priority, Type of work… somehow.
......@@ -586,17 +579,14 @@ Tails community.
Implementation idea: "Deliverable for SponsorXYZ" label.
Example: [[!tails_ticket 10601]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/10601>
* Preserve attachments
Example: [[!tails_ticket 7763]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/7763>
* Preserve embedding of attached images
Example: [[!tails_ticket 17068]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/17068>
* Convert Textile issue description and comments to Markdown
(pandoc can do most of the work see <https://pandoc.org/try/?from=textile&to=markdown>):
......@@ -609,7 +599,6 @@ Tails community.
- bullet lists, including nested ones
Examples: [[!tails_ticket 17241]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/17241>
Textile: <https://www.redmine.org/projects/redmine/wiki/RedmineTextFormatting>
GitLab Flavored Markdown (GFM): <https://docs.gitlab.com/ee/user/markdown.html>
......@@ -617,14 +606,12 @@ Tails community.
* Convert public notes to GitLab comments.
Example: [[!tails_ticket 17121]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/17121>
* Private comments (notes): migrate their contents somewhere,
and make it accessible from the corresponding issue,
in the right place in the discussion.
Example: [[!tails_ticket 16875#note-3]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/16875>
It looks like GitLab does not support private comments.
......@@ -654,7 +641,6 @@ Tails community.
Adding this information to the issue description is good enough.
Example: [[!tails_ticket 15878]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/15878>
* Preserve metadata changes
......@@ -694,12 +680,10 @@ Tails community.
- `source:some/file`
Examples: [[!tails_ticket 17241]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/17241>
* Preserve watchers (as "participants") for open tickets.
Example: [[!tails_ticket 16875]]
→ <https://gitlab.tails.boum.org/tails/tails/-/issues/16875>
It is acceptable to give Redmine users a data file + script to run
in order for them to re-subscribe to the issues they were watching.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment