Create ticket guidlines » History » Version 1
rainerkoenig, 2023-11-24 09:53
First draft to discuss
| 1 | 1 | rainerkoenig | # Create ticket guidlines |
|---|---|---|---|
| 2 | |||
| 3 | ## Template |
||
| 4 | |||
| 5 | Copy this markdown code in the ticket description and use it. The lines with `*text*` are just comments that you can remove or overwrite. |
||
| 6 | |||
| 7 | ``` |
||
| 8 | ## Motivation |
||
| 9 | *describe the problem here precisely, self contained, avoid links to openQA because they will be gone sooner or later* |
||
| 10 | |||
| 11 | ## Scope |
||
| 12 | *name the job groups (with IDs) or product versions that will be affected by this ticket, so everyone knows what this is about* |
||
| 13 | |||
| 14 | ## Acceptance criteria |
||
| 15 | **AC1**: *Acceptance criteria that can be measured* |
||
| 16 | **AC2**: *if needed fill out more acceptance critera* |
||
| 17 | |||
| 18 | ## Additional information |
||
| 19 | *If you have additional hints and tipps on what you expect to be done, write them down here* |
||
| 20 | ``` |
||
| 21 | |||
| 22 | ## Priorities |
||
| 23 | - Chose priorities wisely. |
||
| 24 | - Avoid `Low` because the chance that this will be worked on is also very low. |
||
| 25 | - Remember that [[Backlog_Assistant]] alerts for some priorities if there are no updates for a given period of time: |
||
| 26 | - Immediate: Ticket needs to be worked on and updated daily. |
||
| 27 | - Urgent: Ticket needs to be updated at least once a week. |
||
| 28 | - High: Ticket needs to be updated at least once in 28 days. |