Please allow tickets to be filtered by projects.

Kind regards,

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.

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" ?

Do you think that's possible ?

Thanks in advance for your response.

I-DoIT is a software like GLPI. However, the development of GLPI is progressing much better than I-DoIT and I am considering switching. But then I don't want to start from scratch with my inventory.

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

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

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

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

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)

Hi.

Currently a person can specify if the person wants to get notification via e-mail by clicking on the ticket -> ticket tab -> click on the small envelope icon -> e-mail followup -> Yes/No -> Save. This hides the funcionality very well.

I propose to have a simple "Follow/Following" button on the "Processing ticket" page with the followin logic.

1. Currently not following the ticket. Label is "Follow". After pressing this button, it will change to "Following". Person is added to the "watcher" list
2. Currently following. Label is "Following". After pressing this button, it will change to "Follow". Person remains on watcher list, but e-mail notifications for this specific ticket are disabled for this specific person.

Objects like cable ducts, fillers, maybe even patch panels and KVM switches need to be added to the racks for proper hardware organization and rack display, but in many cases (like cable ducts ecc., we have dozens of them :-) it doesn't make any sense to keep them as separate inventory objects in GLPI.  It would be nice to have some kind of "generic hardware object" or "placeholder" which can be placed as many times as required in a rack.  I don't think this is currently possible.