Would be nice to have the possibility to transfer a location between entities.

Also requested here:

https://forge.indepnet.net/issues/3255

http://forum.glpi-project.org/viewtopic.php?id=26454

Possible this is also in conjunction with 

http://glpi.userecho.com/forums/1-general/topics/700-tranfer-option-between-entities-on-projects/

Keep a session alive while file uploads

https://stackoverflow.com/questions/24541130/how-to-keep-a-session-alive-while-a-file-uploads

http://www.webdevbros.net/2006/12/14/keep-session-alive-with-javascript/

http://www.theserverside.com/discussions/thread/20125.html

File upload and session expires

Hello, I have been testing the file upload component.

I have set the variable in php.ini
upload_max_filesize = 5M

And I have set up a session time of 5 minutes.

I have observed several details in it:

1.- When a file has a size greater than 5 Megabytes and exceeds the 5 minutes of session, this reaches 100% but does not show any message, nor is it attached to the ticket. In other words, the session expires and therefore the file is never uploaded, but does not inform in any way, simply the screen stays static until some action is done and redirects to the login page.

2.- Some types of PDF files do not recognize them as such and displays the message "file type not allowed".

3.- Some very large files at the end and reach 100% does not show any message and does not add it to the ticket.

4.- If I upload a file larger than 5 Megabytes, first I have to wait for it to reach 100% so that it indicates to me that the file size exceeds the maximum. That is to say, it could be configured so that once the file is selected, it validates the size and if it exceeds the maximum that sends a message and does not wait until it reaches 100%.

Suggestions:

1.- Keep the connection active during the time you upload a very large file.

https://stackoverflow.com/questions/24541130/how-to-keep-a-session-alive-while-a-file-uploads

2.- If a file is larger than upload_max_filesize = 5M you should not wait for it to reach 100%, otherwise validate before it starts uploading.

Can the "add to a transfer list" be added to Projects as well, in order to transfer Projects from one entity to another one?

When planning an additional task for a tech, if the selected time frame is already busy, GLPi gives an error (in future versions will be a warning) which is OK, but saves the task anyway (which is not).This renders planning useless, since a tech could be assigned multiple times to the same timeframe.

As this behaviour is acceptable for some users, my suggestion is to add a check either globally or per Entity to allow or disallow tech task planning overlap.

Please check github issue for additional info:

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

It would be useful to have the possibility to set as mandatory the tickets taskso fields when required.

Bonjour,

Nous souhaiterions avoir un bouton d'export au format excel ou pdf pour le diagramme de GANTT.

Cela serait une bonne fonctionnalité au niveau de la gestion des projets afin de montrer à nos supérieurs au format papier A3.

En vous remerciant par avance.

Cordialement
Service Informatique

Hello.

We are using GLPI to manage tickets but users only interact via e-mail.

The authentication is done via LDAP and the support team interacts with the tickets via GLPI.

Recently i added to the template notification the links to download attached documents.

Now the problem.

When the user clicks the link, GLPI asks for user authentication to download the document.

Since users only interact via e-mail and i don't want them to use web interface, you could allow documents download without authentication.

It would be nice because when i want to send some file to users, i need to upload to some service and send the link in the followup.

It would be easier if i just use upload the file to a followup and user receives the link to download it.

Thank you.

Hola desearía que alguno de ustedes pueda integrar una opcion en glpi donde podamos generar las lista de los computadores y a cada uno poder programarles una fecha para su manteminimiento preventivo

It would be nice to have a finer management of the rights in the Knowledge base in order to implement a simple validation workflow. If the rights of writing and publishing could be taken apart, we could have one "writer" profil who would submit (and have his articles not published) and a "publisher" profile who would review all the articles and publish after approval.