Summary: Enhance task planning flexibility by allowing manual entry of any duration in man-days for "Planned duration" and "Effective duration", providing flexibility beyond the current limit of 100 hours (equivalent to 12.5 man-days). Additionally, introduce the capability to define the value of one man-day in hours, for example reflecting the common practice of considering 1 man-day as 8 hours in project management. This improvement provides users with more accurate and customizable task duration representation.

Details:

1. Duration Entry:
• Replace the current time drop-down with a number-entry field, allowing users to manually enter any duration in man-days.
  
2. Calendar Integration:
• Introduce a setting to define the value of one man-day in hours.
• Example: 1 man-day = 8 hours.
  
  
• The man-day definition is taken from the calendar used by the active entity to calculate the days, hours and minutes at other places in the system.

Summary: Enhance the visual representation of milestones in the GANTT plugin by introducing the ability to customize icons and colors. Currently displayed as a generic rhombus, this feature request aims to provide users with the option to select different shapes, potentially using fontawesome.com or a subset of it, and choose colors for a more personalized and informative GANTT view.

1. Icon Selection:
• In the Task window, add a field for typing in or selecting various symbols from a drop-down.
• Empowers users to choose icons that best represent the nature of their milestones.
2. Color Customization:
• Also in the Task window, add a color-picker field to allow users to choose a color for the selected milestone icon.
• Enhances visual clarity and customization, enabling users to differentiate milestones based on color.

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.

Hi folks,

GLPI has been awesome so far but we are missing on thing at this point:

User Story / Usecase:

We have many consumables stored pysically in our location. For every new item we want to manage as a consumable we need to look at the list of our existing consumables and look for the most recent item number we gave a consumable, then add the new consumable and type out the new item number by hand and label the Product with the number. This is tedious work.

Problem:

Currently we have to see through all our consumables to add a new one and give it the correct item number since there are no templates for Consumables where we can use the commonly used <#####> syntax.

Solution:

Add Consumable Templates or an auto incrementing "item number" field to consumables

We would love for you to give this a thought and maybe implement it in a future release. 

Thank you in advance for considering!

Best regards

Patrick

as an overseeing body, i need to see all projecttasks in ProjectTask.php - not just the ones where myself is a taskteam member vua user or group.
please add filter or a view.
thx

how to hide satisfaction survey questions in GLPI

Il manque la barre de recherche pour les catégories ITIL côté self service.

Il faut donc défiler toute les catégories pour trouver la bonne catégorie.

Je pense que c'est un bug car la barre apparait pendant quelques seconde avant de disparaitre. 

E-mail notifications don't contain a semicolon, where a title separates from ticket action.

Example: New ticket test.

Suggestion: New ticket: test

There is a manual way to add semicolon to new tickets, but it would be easier, if it was added by default.

Adicionar recursos de segurança como:

Bloqueio de senha após X tentativas

Captcha para validação de login

Se puede pagar a glpi para que modifique el software, segun mis requerimientos?