+1,
Most of users won't even understand what does the template means!?
IMO, a category must be linked to one and only template, recursively or
specifically!?
*Anthony HEBERT*
/Responsable d'agence
Tel. +33 (0) 666 895 118/
ahebert@teclib.com_<mailto:kevin.degorosti...@5sur5.fr>_
*teclib SAS*
20 rue d'Agen
68000 Colmar
Tel : +33 (0)1 79 97 02 78 / Fax : +33 (0)1 72 70 31 18
On 02/09/2011 14:57, Jean-Francois Sanfacon wrote:
> I think the best option is the second. First the user set the
category, and then he can select a template.
When user want to add ticket, user must select a category wihout
selecting an template. We should keep it simple for user to be more
intuitive.
Template must be associated with category in background.
*De :*glpi-dev-boun...@gna.org [mailto:glpi-dev-boun...@gna.org] *De
la part de* Franci González
*Envoyé :* 2 septembre 2011 02:39
*À :* nini; Liste de diffusion des developpeurs GLPI
*Objet :* Re: [Glpi-dev] Template of tickets and categories
I think the best option is the second. First the user set the
category, and then he can select a template.
One template should can be assigned to some categories and have a
cascade attribute, so the admin can create a template to use to one
category and his sub-categories. Would This simplify the Trey problem?
Regards!
2011/9/2 nini <nini.las...@orange.fr <mailto:nini.las...@orange.fr>>
Hi,
For me, the second soluce is better BUT a template ticket must be
linked with a categorie AND a type of ticket.
You can have a common category for request and incident but the
template will be different.
Yllen
> Message du 01/09/11 22:34
> De : "MoYo"
> A : "Liste de diffusion des developpeurs GLPI"
> Copie à :
> Objet : [Glpi-dev] Template of tickets and categories
>
> Hi,
>
> We are working on templates for tickets in order to set mandatories,
> hidden and predefined fields.
> We have two choices to implement that :
> - Permit to choose a template on ticket creation.
> - Link templates to ticket's categories. Selecting a category will load
> the template.
>
> What do you think about these 2 options ?
>
> Regards
>
> Julien
>
>
>
>
> _______________________________________________
> Glpi-dev mailing list
> Glpi-dev@gna.org <mailto:Glpi-dev@gna.org>
> https://mail.gna.org/listinfo/glpi-dev
>
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org <mailto:Glpi-dev@gna.org>
https://mail.gna.org/listinfo/glpi-dev
--
Francisco M. González
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
_______________________________________________
Glpi-dev mailing list
Glpi-dev@gna.org
https://mail.gna.org/listinfo/glpi-dev
