Commit 5bf480a2 authored by intrigeri's avatar intrigeri
Browse files

Ticket triaging: adjust template phrasing to GitLab

parent 67819293
Hi! Hi!
We've set up an automated process to ask our fellow contributors to update some tickets of theirs, in order to: We've set up an automated process to ask our fellow contributors to update some issues of theirs, in order to:
* better reflect your plans; * better reflect your plans;
...@@ -8,7 +8,7 @@ We've set up an automated process to ask our fellow contributors to update some ...@@ -8,7 +8,7 @@ We've set up an automated process to ask our fellow contributors to update some
* encourage team work and increase the chances that someone finishes the work; * encourage team work and increase the chances that someone finishes the work;
* avoid a human doing ticket triaging and asking you the same questions on each such ticket. * avoid a human doing triaging and asking you the same questions on each such issue.
In particular, this process identifies: In particular, this process identifies:
...@@ -16,12 +16,12 @@ In particular, this process identifies: ...@@ -16,12 +16,12 @@ In particular, this process identifies:
* Reviews waiting for a long time * Reviews waiting for a long time
However, in the current state of things, this process is not able to notice those tickets when their Target version has been repeatedly postponed by our Release Managers. Therefore, the ticket triaging team decided on #16545 to remove the Target version whenever in such cases, when it does not feel realistic. This is what I'm doing on this ticket. However, in the current state of things, this process is not able to notice those issues when their milestone has been repeatedly postponed by our Release Managers. Therefore, the issue triaging team decided on #16545 to remove the milestone whenever in such cases, when it does not feel realistic. This is what I'm doing on this issue.
You now have a few options, such as: You now have a few options, such as:
* Deassign yourself. That's fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this ticket is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :) * Deassign yourself. That's fine. If it really matters, someone else, possibly you, may pick it up later. Then, if this issue is relevant for a Tails team, bring it to their attention; else, forget it and take care of yourself :)
* If you think you can realistically come back to it and finish the work in the next 6 months, say so on this ticket, for example by setting a suitable "Target version". This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today's choice. * If you think you can realistically come back to it and finish the work in the next 6 months, say so on this issue, for example by setting a suitable milestone. This will communicate your plans to the rest of the project and ensure the task pops up on your radar at a suitable time. Of course, you can still realize later that it is not going to work as planned, and revisit today's choice.
Cheers! Cheers!
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