When we are deleting an item from the GLPI recycle bin, for example a computer, 2 ways of deletion are always presented:

• Permanently delete but keep devices
• Permanently delete and remove devices

The issue is that I have always noticed that when permanent deletion is chosen asking to remove the devices together, some items are not excluded, leaving several inventory requirements that will no longer exist behind, such as: Software, monitor and devices

I believe that this behavior is incorrect and that everything related to that equipment should be removed.

I know that there is an automatic action task that cleans software and software versions that are no longer linked to any computer, this partially resolves the garbage left by a deleted computer, for example.

But today there is no automatic task that deletes unlinked orphan devices that were in automatic inventory, I believe that perhaps this is the way to go, to leave them in the GLPI as optional, or to clean them when deleting the equipment.

We need to customize the notification template according to the "ticket.category" value that will be something like "IT>Support", "IT>Maintenance", "General>Other", "HR>Something", etc. So, we need to check if "ticket.category" contains "IT" word (something like ##IFticket.category CONTAINS "IT"##), maybe a function with some kind of regexp can do the job.

Exist a new version 6.6.5

https://github.com/tecnickcom/TCPDF/tags

Hello, I'm starting out in this area of GLPI and Zabbis and I'm trying to integrate my Zabbix with GLPI, I followed the manual

https://www.zabbix.com/br/integrations/glpi#glpi

However, when testing, the error appears and I can't solve it, can anyone help?

Sending failed: TypeError: cannot read property 'session_token' of null

When an item is being assigned to a person, it shows up under "Used items" list in person view, but there's no entry about used items under person's historical view. On the other hand, if an asset's history is being viewed, history tab shows the history of users to whom the asset was/is assigned to.

This would enable to track what has been ever assigned to user during the user's whole GLPI lifecycle, also this would enable a lot easier tracking of assets - for example assets were assigned to someone else by mistake or by somekind of automation mistake. Currently one has to know the asset name/number first.

I find it extremely useful to be able to hide blocks under certain circumstances. However, I would like to suggest the ability to hide blocks based on ITIL Categories. In my case, I only need to display a specific tab for certain types of tickets, and it would be fantastic if I could control which additional field blocks are shown (or hidden in this case) using a comparison operator or a regular expression.

I hope you will consider my feature request. Thank you very much.

Best regards,

When one of our technician plan a task on a ticket, its status is set to 'Assigned (Planned)' but it doesn't stop the SLA clock. So, we asked them to manually set it to 'Pending' with a 'Waiting for planned task' reason but it's sub-optimal. I think having a planned task on a ticket should pause the SLA clock directly.

In the ticketing system, when adding a follow-up to a ticket, you can choose the type of response you wish to use (Create a Task, Add a solution, add a document, ask for validation, etc.). Once you make your selection, you are 'locked' into the choice essentially and if you wish to change your type of response, especially if you have already typed out your reply, you have to copy the text, close the response, select the new response, and paste your reply.

Is there a way to make the choices interchangeable from any category without having to delete what you have you done? The way I have envisioned it is similar to internet tabs. You select the tab you want at the top of your response page and the form changes based on the selection but the textbox remains static throughout without a refresh. 

I hope this makes sense....

Summary: Streamline project code assignment by introducing a checkbox labeled "Increment in subprojects" next to the "Code" field in the project screen. When selected, subprojects created under a master project will automatically receive an incremented code (e.g., "ABCD-01," "ABCD-02"). This enhancement simplifies project code, reducing manual input and ensuring a structured and consistent code assignment across related projects.

Details:

1. Checkbox Addition:
• Introduce a checkbox labeled "Increment Code in subprojects" below the "Code" field in the project screen.
  
  
2. Functionality:
• When creating a subproject by choosing "As child of" and selecting the master project: if the master project has the "Increment in subprojects" checkbox checked, automatically fill the code of the new project with an incremented value.
  
  

Summary: Enhance project visualization by introducing the ability to assign custom colors to projects, tasks, and milestones based on their Project Type. The selected colors should be reflected in both the project table view and the GANTT plugin for improved clarity and visual distinction.

Details:

1. Color Customization:
• In the Project Type definition, alongside the Name and Comments fields, add three color pickers labeled "Project color," "Task color," and "Milestone color."
  
2. Table View Enhancement:
• Display the selected "Project color" in the project table view, surrounding the type of the project, similar to the display of Project Priority.
  
3. GANTT Plugin Integration:
• Utilize all three colors in the GANTT plugin view: "Project color" on the project bar, "Task color" on the task bar, and "Milestone color" on the milestone symbol.