The ungleich support and ticketing infrastructure » History » Version 2
Nico Schottelius, 11/11/2018 11:18 AM
1 | 1 | Nico Schottelius | h1. The ungleich support and ticketing infrastructure |
---|---|---|---|
2 | |||
3 | h2. Status |
||
4 | |||
5 | This article is *IN PROGRESS*. |
||
6 | |||
7 | h2. Overview |
||
8 | |||
9 | In the ungleich infrastructure we use |
||
10 | |||
11 | * "request tracker":https://bestpractical.com/request-tracker to handle customer requests |
||
12 | * "redmine":http://www.redmine.org/ for project management, knowledge base, process documentation, task organisation |
||
13 | |||
14 | h2. New customer request handling |
||
15 | |||
16 | * All customer requests are routed into RT |
||
17 | * The group responsible for the email / topic / queue gets notified |
||
18 | * First person seeing it picks it for answering |
||
19 | * The project manager checks once per day that there is no ticket that is not taken |
||
20 | * If the request only needs an answer, answer it directly |
||
21 | * If the request requires work, create a related redmine ticket for it |
||
22 | ** The assignee of the support request does not have to be the same as in redmine (!) |
||
23 | |||
24 | h2. Ticket handling |
||
25 | |||
26 | 2 | Nico Schottelius | How to handle internal tickets is defined in [[Ticket Handling]] |