I have added 2 fields to ticket object, one from the plugin Custom fields, and one in my own plugin...

I have two problems

a) When we add the column as part of the result (or because we add it in the filter),  the title always put PLUGIN - xxxx and the name of the field....

This is something inside the twig and we can overrride. A normal user don't understand nothing about plugins, and this disturb them.

b) There is no option to rewrite the result (f.ex, to put an specific link)...   

If i define f.ex the Suppliers.Name field, and i want add some info at the end and make a link,  i can't do unles i change the field definition in the query...  

One idea is that we should be able to call the Plugin method for specific fields.... but now the query always put to the field the itemtype = "ticket" (or the object we are displaying)....   Maybe a new option in the search field definition (specific_itemtype),  should work

(Well it works, but i can't apply upgrades without lost the changes and reimplement again).

When you display a supplier, project, ticket, etc... the main information is in the default tab, and when we change to see f.ex the issues of a project, we lost the title of the project or user....

The idea is to change the twig structure and have in the header some useful information  (title, impersonate for users, etc)...

A plus should be the possibility of overwrite this header..

Olá!!

Gostaria de saber se é possível integrar o GLPI com o Jira.

Quando um usuário cria um problema no Jira, quero ver os ativos que pertencem a ele. Isso é possível?. Como eu posso fazer isso?

desde já, obrigado

Our GLPI server is currently configured to send us (the IT pole) the notifications "internally", that is to say that it uses the SMTP connector of our local Exchange server (which is completely cut of the net). The advantage is that users can only view the notifications internally. That said, if there was a way for GLPI to send notifications to IT teams on external emails, it would be a real plus! That would allow, for the data processing specialists, in this type of configuration a follow-up of the notifications of creation of ticket out of the walls of the company.

A request for the possibility of adding components to tickets - they are purchased separately or replaced, and it would be good to have the possibility of connecting such a separately purchased disk, memory chip, graphics card as an item to the ticket.

Actually, components should be full-fledged items.

Currently we can schedule recurring events: monthly, daily, etc.

But there is no option to create a monthly recurring event, every last Thursday of the month. This is a necessary feature I think, especially in the IT world

Hi everyone,

i would like to know if it's possible to have the possibility when we plan a task in a ticket to hide them when it's done or if the ticket is solved ?

I had imagined a checkbox (already check automatically) with the text "hide this task once solved" directly when we add a task in ticket and after have clic on "Plan this task".

Do you think that is possible ? Someone have the same need as me to not overload the agendas ?

Thank in advance.

Steps To reproduce

1. Create a ticket
2. Create a task in ticket
3. clic on "Plan this task"
4. Have the possibility to hide or not the task once is done or if the ticket is solved.

Currently when using '--only-update-existing', deleted users in LDAP are not disabled.

If no arguments are provided, deleted users in LDAP are disabled but also new users will be created.

I like to have the option to sync existing users and disable deleted users in LDAP, this can be done by creating a new argument and calling "AuthLDAP::ACTION_ALL" only.

https://github.com/glpi-project/glpi/blob/751dcfa2c8e54bcd95636c696c0fb30fa6213b5e/src/Console/Ldap/SynchronizeUsersCommand.php#L193

Hi Team,

We would like to configure M365 multifactor enable account as a email notification account in GLPI.

Please help us with a solution. 

For each GLPI release, please add corresponding hash/checksum files for verification purposes.