Welcome to GLPi feature request service.
Please check if the feature has not already been requested.
If not, please describe it

+1

RAZ Button

ChristopheL 3 года назад обновлен 3 года назад 2

I need a button or an other possibility to do a "cleaning data only" tables in the database.

When i install a GLPI on a server, after configuration and testing, i want a button or action to clean only dat tables in databases ant not tables used to configure GLPI.

Thanks.

+1

Helpdesk.html New Fields

Florian 3 года назад 0

Hello,

is it Possible to integrate in the helpdesk.html the follwoing Fields? actually requests opened by the helpdesk.html would not saved. 

Name

Lastname

EmailAdress

+1

Filter tickets by project in tickets listing

Random488 3 года назад обновлен dhrzic 2 года назад 1

Please allow tickets to be filtered by projects.

Kind regards,

+1

Rights for assets status

maxou 3 года назад обновлен 3 года назад 0

Hello,

Is it possible to add an option to add specific status for specific people ?

For example on the dropdown Status the "Valid return" option will be uniquely available for specific groups.

The Technician Team group will not see this button.

The Project Team group will see this button.

Image 397


Is it also possible to create rules to to prevent error during the change of a status, example with this matrice :

When a computer is set to "Supplier - valid return",  can you add a option to make it impossible to return in another section like "Production - on site/at home" ?

Image 398


Do you think that's possible ?

Thanks in advance for your response.

+1

Integrate the mail analyzer pugin

Riesuu 3 года назад 0

This allows when you use the collector, to have only one mail for each response. This is more than convenient.

GitHub - tomolimo/mailanalyzer: Mail Analyzer GLPI Plugin may be used to combine CC mails into one Ticket

+1

Show parent elements in a less contrasted color

Mathieu MD 3 года назад 0

Inline display of tree elements (for example: Root Entity > Group Inc. > My Department or France > Toulouse > Building B) in tables don't allow user to quickly see the relevant information (here, My Department or Building B).

Parent elements should be in a less contrasted color. See screenshots.

https://github.com/glpi-project/glpi/issues/9559

+1

Multiple BaseDN for LDAP/AD start search

Michał Panasiewicz 3 года назад обновлен 3 года назад 1

Add to start search only specific DN:

ou=users, ou=office1, dc=company, dc=org

ou=users, ou=office2, dc=company, dc=org

ou=users, ou=office3, dc=company, dc=org

ou=users, ou=office4, dc=company, dc=org

https://forum.glpi-project.org/viewtopic.php?id=24762

+1

Transfer a entity to another entity, they are no visible

Michał Panasiewicz 3 года назад 0

When you try to transfer a entity to another entity , they are no longer visible and controllable.

In the database, the glpi_entities.entities_id field got the value -1.

A parallel hierarchy of entities has arisen.

GLPI 9.5.6

Look here:
https://zapodaj.net/a2ac0a0aad26c.png.html

+1

New rule for transfer between entities and change status, based on example: status and entities,

Michał Panasiewicz 3 года назад 0

Is it possible, for example, to automatically transfer equipment between entities with rules.
E.g
If the equipment is added to entity "A" and has the status "for transfer", (and other additional criteria also possible) do a transfer to entity "B" and set the status "after transfer"?
So that, for example: a person who add the equipment and is in a subordinate entity, could transfer it further to another entity, but through an automatic transfer rule, as it does not have the right to transfer it to superior entities.

It's not about the rules that apply to fusioninwentory but for equipment, for example, added manually when in this moment do not have agent and is on stock.

Or for equipment that, for example, has not been updated by FusionInventory for a long time

+1

Projects - limit task and sub-project team member selection to parent project team membership

Derry Birse 3 года назад обновлен 3 года назад 1

Under normal circumstances task and sub-project team membership should be limited to the members of the immediate parent project's team.

So if we have a project/tasks hierarchy as follows, with corresponding team members in braces, the bold and underlined team memberships would not be prevented, in Task 3, bill could not be a member of the Task team, because he was not a member of the parent project (Sub-Project 1) team and in Sub-Project 2, peter could not be a member of the sub-project team, because he was not a member of the parent project (Top Level Project) team:


  • Top Level Project (fred, joe, sally, jane, bill)
    • Sub-Project 1 (fred, sally, jane)
      • Task 1 (sally)
      • Task 2 (fred, jane)
      • Task 3 (fred, bill)
    • Sub-Project 2 (fred, joe, peter)

 

Сервис поддержки клиентов работает на платформе UserEcho