Please check if the feature has not already been requested.
If not, please describe it
![](https://cdn.userecho.com/characters/100.png?1)
Permission for technicians insert comments only in private mode.
Permission for technicians insert comments only in private mode.
![](https://cdn.userecho.com/characters/74.png?1)
project
Possibility of controlling access to projects:
- Public - everyone can view, add and modify the project;
- Restricted - everyone can see but only the team can include and modify;
- Private - only the team can access the project.
![](https://cdn.userecho.com/characters/91.png?1)
[GLPI 9.3.3] why item menu disapear in ticket template ?
Hi everyone,
I see in Github topic this is a choice of GLPI developper but have the item section under the locaction in the general template is very serviceable. For me this is a big regression ... We have a chance to see again this item section ?
Thanks for all
![](https://cdn.userecho.com/characters/65.png?1)
MODIFICAR TAMAÑO DE HEADERS, IMAGENES DEL INICIO Y PANTALLA INTERNA
Hola amigos, soy mas maquetadora en html que programadora,
entiendo que este sistema es un .php, y mucha mano no le puedo meter
me gustaria saber de que manera puedo hacer para modificar el tamaño de las imagenes.
estuve viendo que hay bastantes archivos en .css y demas, pero
los modifico sin exito en la visualizacion!
Alguien tiene alguna idea?
gracias!
![](https://cdn.userecho.com/characters/72.png?1)
Close tasks only with a new comment
Allow me to suggest improvements?
It is about the tasks that are included in the tickets, problems and more.
Currently when we add a task with the To Do status and we need to close it later, just click the checkbox to complete the item. This action does not record any record of the date, time, and who did it. Nor in the history of the ticket.
We are directing analysts to add a comment, even though it may occur that the analyst clicks the button by mistake or just to be able to terminate the call (we use the plugins behaviors to block the call solution if there are pending tasks).
My suggestion would be to allow the task to close so only if the analyst includes a description.
The comment would be added in the timeline of actions with reference to the task and would record the name, date and hour that conslusion.
![](https://cdn.userecho.com/characters/110.png?1)
GLpi 0.85.3 generic object
Bonjour je voudrais savoir quel version de generic object est compatible avec glpi 0.85.3
![](https://cdn.userecho.com/characters/80.png?1)
Auto closed ticket only on business day
Ticket to be closed automatically only on business days based on the entity's calendar configuration (Assistance).
![](https://cdn.userecho.com/characters/86.png?1)
Acessibilidade para deficientes visuais com leitores de telas.
Prezados, sou deficiente visual, utilizo o leitor de telas (NVDA), na empreza estamos com a verção 9.1.2 do glpi; estou estudando sobre as novas versões para atualizar, porém, encontrei algumas inacessibilidades do sistema, como por exemplo ao criar um novo ticket, ao selecionar a localização, o leitor de telas não consegue ler as opções da caixa de seleção, dentre outras condições; este mesmo exemplo dado, na versão que uso atual 9.1.2 o leitor faz a leitura normalmente. embora não saiba programar, estou disposto a contribuir para a acessibilidade do sistema, e gostaria de poder contar com a colaboração dos programadores.
![](https://cdn.userecho.com/characters/108.png?1)
Notify email by source based
I have the GLPI 9.3.3 deployed in a company of 170 employees.
Eventually, some employees do not register the ticket, and the technician has to register the ticket by placing the user as the requester and changing the "Helpdesk" source to "direct / skype / phone".
Is there any way via business rules or otherwise, for when a ticket is registered and the source is not helpdesk, I set up a template informing the user that the technician needed to open the call on his behalf and becoming aware of the need to register the ticket.
Thankful!
![](/s/cache/68/f1/68f1362dcb4371d444a903fc710b3933.png)
Logs of a cloned object (by an entity transfer) should states it is a clone
(Note: I already opened an issue on official issue tracker but was asked to post on Userecho to see if it worth it. So here it is)
When the entity transfer wizard is cloning objets, an explicit "Cloning from object x" event should be added to clone object's logs.
I got into this when transferring a computer to another entity. That computer was attached to documents (and contracts) which where cloned into the destination entity.
Steps to reproduce (my experience, variations may also works)
- - Have the following entities:
- Entity E1
- Entity E2 (as a sub-entity of E1)
- Create computer C1 into entity E1
- Create computer C2 into entity E1
- Create document D into entity E1 (ID=726, used below)
- Attach document D to computers C1 and C2
- Transfer C1 to entity E2
Actual result
Computer C1 is now into entity E2.
A new document D' is created into entity E2 as a copy/clone of document D (the latter stays in E1) with ID=727 (in my example)
While cloning the document D, GLPI clones D_'s logs: it creates new events rows with new IDs keeping the original dates and other informations, but it alos adds two new events "Add the item" and "Change Entity E1 (0) by Entity E1 > Entity E2 (1)" timestamped at the date the transfer was performed.
Logs of D:
8641 2016-03-09 10:54 User (8) Computer Add a link with an item: Test computer2 for entity transfer (409)
8625 2016-03-09 10:46 User (8) Computer Add a link with an item: Test computer1 for entity transfer (408)
8624 2016-03-09 10:45 User (8) - Add the item
Logs of D':
9320 2016-03-09 11:00 User (8) Entity Change Entité racine (0) by Entité racine > FooBar (1)
9319 2016-03-09 10:54 User (8) Computer Add a link with an item: Test computer2 for entity transfer (409)
9316 2016-03-09 10:46 User (8) Computer Add a link with an item: Test computer1 for entity transfer (408)
9315 2016-03-09 10:45 User (8) - Add the item
9314 2016-03-09 11:00 User (8) - Add the item
We see that events 8624, 8625 and 8641 gets copied to D' as-is (respectively as 9315, 9316 and 9319) and that events 9314 and 9320 are added.
Proposition
I suggest that logs of that D' object states it was created as a clone of D.
The Event 9314's label should be "Create the item as a clone of Document 726" or something similar.
Context informations
GLPI version: 0.90.1
Сервис поддержки клиентов работает на платформе UserEcho