Please check if the feature has not already been requested.
If not, please describe it
Show parent elements in a less contrasted color
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.
Multiple BaseDN for LDAP/AD start search
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
Transfer a entity to another entity, they are no visible
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
New rule for transfer between entities and change status, based on example: status and entities,
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
Projects - limit task and sub-project team member selection to parent project team membership
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)
- Sub-Project 1 (fred, sally, jane)
Field owner for devices
Is it possible to add the "Owner" field in the characteristics, which is the field where the user has the equipment in stock?
So that you can globally search for equipment / devices / sim cards / phones owned by a given user ??
"Follow" button in the "Processing ticket" view
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.
Support generic hardware objects/placeholders which can be placed multiple times in the racks
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.
Restrict project visibility to associated groups, users or teams (implement permissions like for tickets)
The access to projects can currently be restricted only by putting them into different entities - however as you all know, it is very difficult to manage fine-grained entities and the possibilities are quite restricted.
It would be a great feature to add the possibility to restrict project visibility to associated groups, like it is already possible for tickets; e.g. it could be realized for "manager groups" or alternatively for Project Teams or single users.
User Story: The CIO manages projects in GLPI. He doesn't want that all IT can see all projects. He decides to add groups or single users as managers to the project (or alternatively defines the project team). In the profiles configuration, Technicians have the (newly proposed) permission "See group projects" and thus can access only their project.
Rules to link a computer to a user to an asset
We use upn for user login and use SSO. Our upn and sammaccountname are different on our AD.
On fusion inventory, the computer goes up, the user also, but this one, is not linked to the user... I cannot use the part "My items of GLPI", nor the other plugins to manage correctly my park.
Can you develop a rule engine to assign the equipment to the user according to his upn.
thank you
Customer support service by UserEcho