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

+5

please add pgp support

Stefan Krüger 6 years ago 0

Hello, it would be very nice if you add pgp/gpg support to sign/crypt/encrypt mails like other tools (eg otrs). Nowadays you don't know if that mail from our (IT)-Support or from somewhere else, so when it signed you know that. The same with encryption, when you write a ticket it is sometimes very helpfull to encrypt the mail (eg for password or tokens).

best regards

+5

Plugins - Check for a newer version

tyrone wyatt 7 years ago updated by Curtis Conard 1 year ago 1

Create 'Check for a newer version' button on Plugins page. 


Create 'checkpluginupdate' automatic action. 


Use the Plugins Catalog website for list of plugin versions. 

+5

Improve search criterion with drag and drop

tyrone wyatt 7 years ago 0

When adding a search criterion with a global search criterion they are added in order. 


Unfortunately this means all search criterion are together and all global search are together.


A modern drag and drop of search criterion would fix this issue.


Image 126


+5

Diff implementation to tickets etc

piotrlg 7 years ago 0

At the same time I'm using Redmine and GLPI to manage IT projects. One of the problem with GLPI which is nicely solved in Redmine is showing the difference after updating the ticket or whatever in GLPI is to change. Redmine tells me exactly the 'diff' between old and new version of the ticket, change etc. In GLPI the only thing I know is that something has changed, but had no idea what was it. So it would be nice to see a diff (link to page with diff?), which could show the exact last change (what was changed, who made it and when - just like wiki pages).


I know there is History, but it does not show sufficient information.

+5

​Enhanced operations regarding assistance objects relationship

Tomás Abad 7 years ago updated by tyrone wyatt 7 years ago 3

Good morning,


Nowadays with GLPI v9.2.x it's possible to make the following relations between the different assistance objects (most of them are possible in GLPI v9.1.x, but not all of them).


GLPI v9.2 Assistance Objects RelationshipGLPI v9.2 Assistance Objects Relationship


These relationships are possible, yes, but make them are a tedious task in many cases.


    Example #1:

   The user Alice calls with a problem in Computer#1. The technician Bob opens a new Ticket#1 and link it with Computer#1. Afterwards, other users call with the same problem in Computer#2, Computer#3, Computer#4,... and Computer#20. Bob must realize the same operation (link Ticket#1 with Computer#n) twenty times.
    Example #2:

   Alice, from our branch office in Paris request us twenty computers (Computer#10, Computer#11,...,Computer#29) located in our central warehouse. Alice didn't open a ticket for that so Bob creates a new Ticket#1 (service request) to track the shipment. In the best case Bob must realize the same operation (link Ticket#2 with Computer#1n) nineteen times.


Other times the relationship can only be established from one end.


    Example #3:

   Bob needs to link the Computer#1 to the Ticket#1, which already exists. He must remember that is only possible to do from the Tickets Management; from Assets Management it is only possible to create new tickets linked with an asset but not to link an asset with an already ticket.


As I say, to make the relationships is possible, of course, but when the number of element to connect is elevated the process becomes into a tedious thing. This is why I suggest two improvements.


Suggestion #1 > Take a selection of an object A query as the set of elements to link to a previously created B object.


Following with Example #2, it would be possible to reduce the number of operations to  four or five in this way.


1. In 'Home > Assets > Computers' make the query "'Characteristics - Name' contains '^Computer#1' Or 'Characteristics - Name' contains '^Computer#2'".
2. Select all computers from the query result.
3. Choose the massive action "Associate with ticket...".
4. Choose the ticket with which to associate the computers; Ticket#2.
5. Confirm action.

Following the previous picture, It should be created the following new massive actions.


  • Massive Actions for Assets
    • Associate with Ticket...
    • Associate with Problem...
    • Associate with Change...
    • Associate with Problem...
    • Associate with Knowledge Item...
  • Massive Actions for Tickets
    • Associate with Problem...
    • Associate with Change...
    • Associate with Task # of Project...
    • Associate with Knowledge Item...
  • Massive Actions for Problems
    • Associate with Change...
    • Associate with Knowledge Item...
  • Massive Actions for Changes
    • Associate with Project...
    • Associate with Knowledge Item...
  • Massive Actions for Projects
    • Associate with Knowledge Item...
Suggestion #2 > Make bottom-up relationships


Following with Example #3, it would be possible associate Computer#1 with Ticket#1 from Computer#1; Bob will never need to think before where to go to do the association. From 'Home > Assets > Computers > Computer#1 > Tasks Tab' Bob could create a new ticket associate with Computer#1 or associate Computer#1 to a previously existing ticket.


Following the previous picture, It should be created the following new actions.


  • Assets
    • 'Tickets' tab  
      • Associate with Ticket...
    • 'Problems' tab
      • Associate with Problem...
    • 'Changes' tab
      • Associate with Change...
    • 'Problems' tab  <-----------------------------(***This tab is missing***)
      • Associate with Problem...
    • 'Knowledge base' tab
      • Associate with Knowledge Item...
  • Tickets
    • 'Problems' tab
      • Associate with Problem...
    • 'Changes' tab
      • Associate with Change...
    • 'Project tasks'
      • Associate with Task # of Project...
    • 'Knowledge base' tab
      • Associate with Knowledge Item...
  • Problems
    • 'Changes' tab
      • Associate with Change...
    • 'Knowledge base' tab
      • Associate with Knowledge Item...
  • Changes
    • 'Projects' tab
      • Associate with Project...
    • 'Knowledge base' tab
      • Associate with Knowledge Item...
  • Projects
    • 'Knowledge base' tab
      • Associate with Knowledge Item...


That is all. Thanks in advance and best regards,


+5

solution mask add time (create a task in done state)

Armin 8 years ago updated by Arthur Schaefer 7 years ago 2

If i get a small ticket from user over web interface which i can solve directly. I have to create a task with state done for time recording. It would be great to add this time 3 min / 5min / 7min directly in solution mask.

Example Solution: Off / On the printer solves this problem... but i have the time for read the ticket. I don't want to waste time on time recording task too.

+5

Manage containers

Walid Nouh 8 years ago updated 8 years ago 0

Separate virtual machines and containers.


Should be considered as containers, as retrieved by FusionInventory agent :

- Docker

- LXC & LXD

- Solaris Zones (https://en.wikipedia.org/wiki/Solaris_Containers)

- OpenVZ & Virtuozzo (https://en.wikipedia.org/wiki/OpenVZ)


+5

Display field cartridge Average time in stock/in use

domg 8 years ago 0

Hi,


Add field average time in stock and in use in cartridge list.


Thanks in advance

+5

Notifications - latest item

Piotr Rybak 8 years ago updated by yves tesniere 7 years ago 1

Is it possible to get access to latest item (followup/task) that was added within ticket/change/project?

I want to prepare notification template that will have the lastest followup at the top and rest of the conversation below to have better notifications from the system.


Same applies to tasks in changes/projects/tickets.

+5

Add a parameter to show/hide prefix for column title

Eric Coutier 8 years ago 0

In version 0.8xxx, the column titles weren't prefixed in "list" mode. For example, "Purchase date". Now, in 0.9, column titles are prefixed with the name of the source table name. But it makes columns header very high.

Perhaps it's possible to put a parameter to avoid that.