Hi Julien,
I think option 2 is better, but I would imagine a equivalent to
notifications (templates and notifications separated).
An example :
- My company manages customers
- I've got a set of global categories (ie root entity, recursives)
- I apply a template for this category
- For one
Le 01/09/2011 22:32, MoYo a écrit :
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.
- Will the category be, then, limited to a sub-tree,
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
Le 02/09/2011 08:03, Remi Collet a écrit :
Le 01/09/2011 22:32, MoYo a écrit :
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.
- Will the category
; 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
Le 01/09/2011 22:54, David DURIEUX a écrit :
Le Thu, 01 Sep 2011 22:32:34 +0200
MoYom...@indepnet.net a écrit:
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
Le 01/09/2011 22:56, Jean-Francois Sanfacon a écrit :
Selecting a category should be better. When you change category, all extra
field appear for this one.
Extra fields will not be added. Templates permit only to predefined or
hidden fields and set mandatory ones.
So as admin, you can
Le 01/09/2011 22:32, MoYo a écrit :
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
Le Thu, 01 Sep 2011 23:07:03 +0200
MoYo m...@indepnet.net a écrit:
Le 01/09/2011 22:54, David DURIEUX a écrit :
Le Thu, 01 Sep 2011 22:32:34 +0200
MoYom...@indepnet.net a écrit:
Hi,
We are working on templates for tickets in order to set mandatories,
hidden and predefined fields.
We have
The first option sounds better and would allow for more flexability,
especially in my organization.
- Trey
On Sep 1, 2011 3:33 PM, MoYo m...@indepnet.net wrote:
Hi,
We are working on templates for tickets in order to set mandatories,
hidden and predefined fields.
We have two choices to
Le 01/09/2011 23:31, Trey Dockendorf a écrit :
The first option sounds better and would allow for more flexability,
especially in my organization.
Could you explain us why ?
Thanks
Julien
- Trey
On Sep 1, 2011 3:33 PM, MoYo m...@indepnet.net
mailto:m...@indepnet.net wrote:
Hi,
We
For my org we have 100s of categories total for all entities. There are
maybe 30 for the top level entity and up to 100 in some of the sub entities
managed by seperate admins. So for me to create templates for all those
categories would be a nightmare. Ive setup our glpi to be very distributed
12 matches
Mail list logo
