The option to create a problem from a ticket already exists.

The option to create a change from a problem already exists.

But no option to create a ticket from a problem.

Create a ticket from a problem would be very useful feature when logging repeat tickets of the same problem.

An example would be that the internet is down for all users, the hotliner or technician would need to follow complete the process to log new tickets:

Current process: Create a new ticket manually by entering the requester, category, title, description, submit and adding the ticket to the problem.

New process: Click click create a ticket from problem, enter requester and submit.

I have used the option in another service desk package in the past and this feature is a real time saver. This feature encourages all tickets to be logged by service desk operators and technicians.

A mock up of Create a ticket from a problem.

If it's possible, it'll be helpfull to include the complete email form (Name-Surname<username@email..>) or just the NameSurname part into the received tickets for non-existent GLPI users

Hi ,

I'm just getting acquainted with the GLPi world. I have digged documents about my problem but couldn't find .

World is more the Computer asset. Servers, Virtual servers lots of types. I can created those asset types by generic object plugin.

But is it possible to Move an asset from Computer type to (Custom Created) Servers type.

Best Regards

Bahadir

Hello

It would be useful to add a picture associated with model and display it in computers / network / device / phones

A new setup / pictures / 

Add a new picture

Select model associated

We can define unicity on some fields, but their value can still be empty.

On another hand, we may want to set some fields as mandatory; but without any unicity.

Maybe could we consider upgrading the unicity feature to a more generic "fields setup", with unicity and mantadory (at least). Such fields must be marke as required on the html side (using the "standard" * mark, and the relevant html attribute.

Improbe surveys with more questions about of services, etc.

Language by Entity - Define language by entity with more relevant is user language, second is Entity and the last is GLPI Default Language

This will be helpfull for who use GLPI with Anonymous Ticket. When tickets came from specific e-mail address the rule move to specific Entity so the e-mails notifications will be sent following the language of the entity and not from GLPI Default language.

Firstly, thank you for this amazing application.

Please add a template option for 'Problems'. It would be so helpful.