Feature #1331

Templates for tickets

Added by moyo almost 5 years ago. Updated over 2 years ago.

Status:Closed Start date:
Priority:Normal Due date:
Assignee:moyo % Done:

100%

Category:Helpdesk
Target version:0.83

Description

- Définition d'un gabarit glpi_tickettemplates (id,name,entities_id,is_recursive,comment)
- Définition des champs à cacher glpi_tickettemplatehiddenfields (id, tickettemplates_id, num)
- Définition des champs prédéfinis glpi_tickettemplatepredefinedfields (id, tickettemplates_id, num, value)
- Définition des champs obligatoires glpi_tickettemplatemandatoryfields (id, tickettemplates_id, num)

- Ajout d'un lien sur la création pour choisir le template et chargement de celui-ci.
- Gestion d'un template par défaut : oui. A voir si on le gère globalement ou par entité.

- Gabarits pour les post-only : OUI


Related issues

blocked by GLPI Documentation - Task #3145: Templates for tickets Closed 09/21/2011

Associated revisions

Revision 15481
Added by moyo over 2 years ago

prepare DB for ticket templates see #1331

Revision 15531
Added by moyo over 2 years ago

prepare ticket templates see #1331

Revision 15532
Added by moyo over 2 years ago

minimal searchoption for ticket template see #1331

Revision 15534
Added by moyo over 2 years ago

work on ticket template tabs see #1331

Revision 15535
Added by moyo over 2 years ago

tickettemplate objects + tabs see #1331

Revision 15537
Added by moyo over 2 years ago

more work on ticket template definition / hidden and mandatory ok : see #1331

Revision 15538
Added by moyo over 2 years ago

forward entity info for ticket template see #1331

Revision 15547
Added by moyo over 2 years ago

work on ticket templates + unified method to display datas : see #1331 and see #2662

Revision 15607
Added by moyo over 2 years ago

adapt ticket template DB scheme see #1331

Revision 15608
Added by moyo over 2 years ago

reorder fields for ticket templates see #1331

Revision 15612
Added by moyo over 2 years ago

load predefined values for ticket templates see #1331

Revision 15617
Added by moyo over 2 years ago

mark mandatory fields see #1331

Revision 15618
Added by moyo over 2 years ago

manage hidden fields for templates
see #1331

Revision 15619
Added by moyo over 2 years ago

more work on see #1331

Revision 15622
Added by moyo over 2 years ago

ticket templates for post only see #1331

Revision 15629
Added by moyo over 2 years ago

permit to choose itemtype / items_id on ticket templates see #1331

Revision 15673
Added by moyo over 2 years ago

choose relative date for due_date for ticket template
see #1331

Revision 15674
Added by moyo over 2 years ago

Manage due_date on relative computation see #1331

Revision 15675
Added by moyo over 2 years ago

ticket template preview for central see #1331

Revision 15676
Added by moyo over 2 years ago

work on ticket templates see #1331

History

Updated by moyo over 3 years ago

  • Assignee deleted (8)
  • Target version changed from Unplanned to 33

Updated by jmd over 3 years ago

- Définition de gabarits de tickets :

- possibilité de masquer des champs inutiles
- option mandatory
- valeurs prédéfinies

Updated by jmd over 3 years ago

  • Target version changed from 33 to 0.83

Updated by moyo about 3 years ago

- Définition d'un gabarit glpi_tickettemplates (id,name,entities_id,is_recursive,comment)
- Définition des champs à cacher glpi_tickettemplatehiddenfields (id, tickettemplates_id, num)
- Définition des champs prédéfinis glpi_tickettemplatepredefinesfields (id, tickettemplates_id, num, value)
- Définition des champs obligatoires glpi_tickettemplatemandatoryfields (id, tickettemplates_id, num)

- Ajout d'un lien sur la création pour choisir le template et chargement de celui-ci.

- Gabarits pour les post-only ?

Updated by moyo about 3 years ago

  • Subject changed from Gestion de gabarits pour les tickets to Templates for tickets

Updated by guy.bertrand@banctec.com almost 3 years ago

Un commentaire pour augmenter cette fonctionnalité: il serait très utile de permettre que plusieurs genres de billet d'assistance soient actifs en même temps, qui utilisent des gabarits différents.

C'est à dire:
Assistance:
+ (nouveau)
-Demande d'achat nouveau ordinateur
-Problème application #1
-Problème mon PC
-Nouvel employé(e)
etc.

Chaque genre de requête a ses propres champs requis, capacité d'ajouter des nouveaux champs, cacher des champs non-utilisés, etc. Ce qui serait encore plus idéal, c'est que l'on puisse ajouter des champs, qui sont ajouté dans la BD de façon automatique et transparente.

Updated by moyo almost 3 years ago

  • Assignee set to moyo

Updated by moyo over 2 years ago

  • Status changed from New to Assigned
  • % Done changed from 0 to 80

Updated by moyo over 2 years ago

  • % Done changed from 80 to 90

Updated by moyo over 2 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 90 to 100

Updated by moyo over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF