| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | == Management of tickets == |
| | 4 | RUF meetings will be held quarterly. Each meeting constitutes a "milestone" in trac terms. A milestone is a collection of tickets. When someone creates a ticket, the milestone will by default show the next upcoming RUF meeting. |
| | 5 | |
| | 6 | Different sets of reports are available to support easy assessment of tickets. Reports are created based on ticket properties like milestone, priority, type and component. |
| | 7 | |
| | 8 | Assessment of tickets take place in RUF meetings, where tickets are either rejected or accepted. Rejected tickets are tickets that are considered irrelevant, e.g., out of scope for the project or duplications of other tickets. Accepted proposal will be prioritized and then possibly be assigned to a project for implementation. All tickets assigned to a project will be collected in a separate milestone just for this project. |
| | 9 | |
| | 10 | The picture below describes the management of versions, publishing and development. |
| | 11 | |
| | 12 | {{{ |
| | 13 | #!graphviz.dot |
| | 14 | digraph G { |
| | 15 | rankdir=TB; |
| | 16 | |
| | 17 | assessment[shape=diamond]; |
| | 18 | prioritization[shape=diamond]; |
| | 19 | |
| | 20 | new_ticket -> assessment; |
| | 21 | assessment -> rejected_ticket; |
| | 22 | assessment -> accepted_ticket; |
| | 23 | |
| | 24 | accepted_ticket -> prioritization; |
| | 25 | |
| | 26 | prioritization -> assigned_to_project [label="priority level high"]; |
| | 27 | |
| | 28 | } |
| | 29 | }}} |
