Historique de la page
| Sommaire |
|---|
L'indexation des tickets et des FAQ est réalisée par la librairie Lucene.
...
The expiration and archiving of tickets is done by the asynchonous ant tasks expire-tickets and archive-tickets (see 03 Administration) using the properties below (set in
/properties/config.properties
...
Latence avant expiration
...
).
Properties
Latency before expiration
The time before a ticket is automatically expired by the application if the closure of a ticket is not approved by its owner:
| Bloc de code |
|---|
|
...
#expiration.timeLimit=14d |
| Astuce |
|---|
Les unités admises sont Allowed units are m (month) et and d (day). |
Latence avant archivage
Latency before archiving
The time before a ticket is automatically archived by the application once approved or expired:
| Bloc de code |
|---|
|
...
#archiving.timeLimit=1m |
| Astuce |
|---|
Les unités admises sont Allowed units are m (month), d (day) et and h (hour). |
Mise en place de l'expiration et l'archivage
...
Commands
See: 03 Administration
Expiring non approved tickets
Expiring non approved tickets is done by the ant task expire-tickets, which sould be called periodically. For instance, on a Unix system from a crontab:
| Bloc de code |
|---|
02 * * * * root /usr/local/helpdesk/helpdesk-cron.sh expire-tickets
|
Archiving approved or expired tickets
Archiving tickets is done by the ant task archive-tickets, which sould be called periodically. For instance, on a Unix system from a crontab:
| Bloc de code |
|---|
03 * * * * root /usr/local/helpdesk/helpdesk-cron.sh archive-tickets
|
...