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.
  
  

BeyondTrust Remote Support is an HelpDesk tool, to connect to remote machines securely.

16.000 installations in the world, some of the customers use also GLPI.

It could be a good option to connect directly from a ticket to the machine.

An extended API exists in Remote Support to start this connection.

Implement the abillity to prefill Ticket Forms via URL GET Parameters.

For Example to use in E-Mail Links.

Example:

ticket-system.de/front/ticket.form.php?subject=Ticket_Title&description=Prefilled&category=IT

Currently, tasks can only be assigned to one project and using the usual action button, moving them to another project is still impossible.

Advantage: Unfinished project tasks could thus be moved to a subsequent project and the project could still be considered complete without having to create duplicate tasks.

Possibility of sharing pre-designed Filters/Markers between users

Good morning, the possibility of being able to share among selected nominative users the different filters/Bookmarks that are created as predefined queries is suggested. Currently, they must be made public to all personnel who use GLPI or private. It would be useful to be able to share it among selected users of the same team, etc. so you don't have to create the same query for different logins in a custom way.

Thanks in advance.

Enable notifications queue through API request. So we can monitor how many notifications that can be error-related.

Generate ticket after change of the hardware collected by glpi agent

We diligently use your excellent certificate tracking tool and the knowledge base tool.

As part of the management of renewal and follow-up of certificates, we have procedures to help with renewal. For this, we use an entry from the knowledge base.

Unfortunately, when managing domains, we cannot associate a knowledge base entry to it.
When managing domain records, we cannot associate certificates, knowledge bases or associated items to it.

Would it be possible to activate these modules on the pages concerned?

(Here is a request that might look like this request. ticket )

Best regards

source ticket:https://github.com/glpi-project/glpi/issues/14891

We've seen that we can associate tickets and other types to a ticket. But how to distinguish e.g., between a change that was a result of a ticket and a ticket because of a change? 

One can associate changes in tickets but there is no indication if the change was the result or the (root) cause of the ticket.

Wouldn't it be a useful idea, to specify the cause of a ticket? And causes could be changes (most likely), or other objects like project tasks, release, etc.

Also, in the solution-entry one can specify a solution type but no relation to a type (e.g. a change). 

Wouldn't it be a useful idea, to specify the solution of a ticket and link the "solving" item (e.g. a change)?