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

business rules : add new criterion "Technician - User DN" with "regular expression matches"

Because with the "user DN" of the Active Directory together with regular expressions it gives you enormous power to customize various rules

Today it is possible to promote a ticket, however it is necessary to give permission to update followups in the profile to enable the icon, but it is not always interesting to enable this permission, it would be interesting if there was an option to permit only this feature.

Hoje é possível promover um ticket, porém é necessário dar permissão para atualizar acompanhamentos no perfil para habilitar o ícone, mas nem sempre é interessante habilitar essa permissão, seria interessante se houvesse uma opção para permitir apenas esse recurso.

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

Can't change date format separator.

In current version of GLPI (9.3.3) it is not able to change date format to custom settings (Setup - General - Default values: Date format, or profile - Personalization - Date format). There is only selection of date format from only 3 options:

1. YYYY-MM-DD
2. DD-MM-YYYY
3. MM-DD-YYYY

Problem is especially with separator - (dash) which is not configurable. For example in Slovak/Czech language we use . (dot) as a separator for date and not dash:
29.11.2018

Another languages use / as separator etc.

So it would be great to have option to also change separator for date format.

Describe the solution you'd like

Please add option to change separator for date format. Or better to able to also use custom php format:
http://php.net/manual/en/function.date.php.

For example Wordpress uses 4 predefined options a you can also use your own custom which is great:
https://www.wpbeginner.com/beginners-guide/how-to-change-date-and-time-format-in-wordpress/

As I am working towards training users to build KB Articles in the improved Knowledge Base, There are some custom formatting settings I would like to see used across the board. 

It would be nice if we could create a KB Template per entity so that formatting could be the same when trained technicians create new KB Articles. 

For Example: Default KB Template

(Company Logo)

PLEASE PLACE YOUR KB HEADING HERE 

The body of this knowledge base article should be in italics. Please use this formatting.

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.