You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we set up the target ticket, in the target section of the form, we can choose data from a list of available tags. These tags are question and answer tags only. We can't select the description of the sections and either use a global GLPI variables available in other GLPI contexts like {{ user.login }}, {{ user.fullname }}, {{ user.email }}, {{ user.phone }}, {{ user.phone2 }} (this variables are available, for example, in the task template definition).
In some ocasions we would like to add data from these global GLPI variables or the description of the section in the ticket target as extra information for the technician. Now, when we need this information we have to create a question asking this data.
We use GLPI for a service request of all the areas and departments of our institution. Not only for IT request and incidents. For this reason, a feature like that it would be very usefull for us.
The text was updated successfully, but these errors were encountered:
When we set up the target ticket, in the target section of the form, we can choose data from a list of available tags. These tags are question and answer tags only. We can't select the description of the sections and either use a global GLPI variables available in other GLPI contexts like {{ user.login }}, {{ user.fullname }}, {{ user.email }}, {{ user.phone }}, {{ user.phone2 }} (this variables are available, for example, in the task template definition).
In some ocasions we would like to add data from these global GLPI variables or the description of the section in the ticket target as extra information for the technician. Now, when we need this information we have to create a question asking this data.
We use GLPI for a service request of all the areas and departments of our institution. Not only for IT request and incidents. For this reason, a feature like that it would be very usefull for us.
The text was updated successfully, but these errors were encountered: