Improved quick fill of follow up information to optionally include state choice in Follow Up template.

So for example, follow up template could be:

Name: Review

Content: State has been changed to Review

Comment: quick change to review state

Source: Direct

Private: No

State: Review

Then all technician would need to do would be select Review from follow up templates and click Add button.

Allow the specification of a default approval group/user and default minimum approval validation requirement. If a template has a default approval configuration, then changing status to Approval should also generate an approval request based upon the default approval configuration.

Add hooks within the global search engine and KB search engine to allow plugins, to easily provide search results in the correct format for adding to the result list.

e.g. to allow TAG plugin (or any other plugin) to generate results for global and KB search

I can tag items such as Project Tasks and KB items but I cannot search for them or even filter for them via TAG, so being able to tag them is almost pointless. 

Can we add the ability to search by tag in the global search as well as in the KB search. Could be by prefixing with # like #hashtag in the search or simply by treating the search text as a possible tab.

May be dependent upon the Idea - CHANGE add start and end dates also being implemented. But could use resolve date for check.

Ability to associate change freeze calendar with entity and check change planned start and end dates against change freeze calendar.

Possibility to create warning banner at top of every change record tab saying something like:

”Change window is in change freeze, please seek CIO approval to proceed.”

Like ServiceNow would be helpful to have a button either on Processing tab or Change tab which moves ticket to next status (except when awaiting approval) and creates a follow up indicating that this has happened.

if current status was New then button text would say “Move to Assessment” say and clicking this would update the ticket status to Assessment and add a follow up which says something like “Status changed from New to Assessment”

Make ticket processing a little quicker

In the Project global and project Kanban view, it would be very beneficial to be able to filter on more that just the Name field. 

For example, a Kanban view equivalent of MyTasks

It would also be good to be able to filter as follows:

Kanban filters:

• Title content
• Priority value  (will only apply to projects/sub-projects)
• Code value (will only apply to projects/sub-projects)
• Milestone value (will only apply to tasks)
• Type value
• User value (will only apply to projects/sub-projects)
• Group value  (will only apply to projects/sub-projects)
• Project team and/or Task team member value
  
• Show top level projects only, all projects only, all tasks only or all projects and tasks (default)
• Date filter? more tricky, possibly a range

Filters would preferably use the built in filter/search capability (as per top level project list view filtering or My Tasks filtering) or could possibly take the form of a string:

title:<contains this> priority:<contains this> user:<contains this> start:<date string> end:<date string>

Would also be beneficial to be able to filter in the "Project tasks" view

I find this plugin which can do it.

Set a lifecycle for a period of time specified by your administrator. Separately for hardware groups.

I have a problem, some user can not send mail to GLPI e-mail, so i want to use my another system. That's cloud system, i want to give shared link from Cloud to GLPI, where i want to store new tickets.
Anyone can help me?

Can you give me plugin name or link?

Do you have idea?

Thank you.

When user is creating a ticket at the upper level entity, the form could display an entity field enabling to choose a child entity to register the issue.
 
The form should then reload with the corresponding entity model, without the need to specifically change the entity at the upper right corner of the screen.