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

+4

CHANGE add start date and end date

ylagva 10 years ago updated by Derry Birse 4 years ago 1

It would be ITIL to add the time period of the change.

+4

Add parenthesis to request

ylagva 10 years ago updated by Tomás Abad 7 years ago 6
Hello,

It could be very useful to add parenthesis to request module allowing to create advanced request.

Example : requester is user and requester is not (x or y or z)
ticket by technician group is not ( x or y or z) and (requester is t and ticket type is p)
+4

statistics

alrone rhyn 10 years ago updated by Javier Samaniego 10 years ago 1

Hi !
It would be awesome to display statistics with multiple criteras :
For example, how many tickets by whom by location.

Thx a lot !

+4

To give rights to watchers to view tickets where they appear independently of entities

Tomolimo 10 years ago 0

Hello,

Imagine you have plenty of end-users with rights only on the self-service (=simplified) interface.

Imagine you have plenty of entities, and end-users have only 'post-only' rights on one of theses entities.

The need is to give the possibility to end-users to view (and depending on rights to edit) tickets for which they don't have the formal rights (different entities) when and only when they are assigned as watchers on these tickets.


Example:

Two users: U1 and U2 have respectively 'post-only' rights on entities E1 and E2. Let's create one ticket T1 in entity E1 with U1 as requester. In this case U2 cannot see (nor edit) T1. In this case T1 can't be seen by U2 (we can't even assign U2 as watcher due to entity restrict).


1) we would like to be able to assign any user (whatever entity rights he may have) as watcher.

2) we would like to permit U2 to be able to view and add followups to T1.


More:

Of course this should also be possible via groups as watchers. When users belonging to a group (assigned as watcher on T1) don't have formal entity rights.


This need can be linked to the 'carbon copy' of users at ticket creation: when a user is creating a ticket he/she may add any other user to be watchers (independently of entities).


Thank you,

Regards,

Tomolimo

+4

Coloration tâche dans un ticket

Loïc FONTAINE 10 years ago updated by ylagva 10 years ago 1

Il serait pratique de colorer une tâche dans le calendrier en fonction de la priorité du ticket auquel elle est associée

+4

Chronometer Task

Cristiano Reis 10 years ago 0

I think that multi chronometer for tasks. The intension is a better control
of task. Multi tasks running at the same time. exemple Stop the task 1 e
continue the task 2.

Some times the user call e dont have ticket. I could start the chronometer
and when stop i would have the option to create a ticket.

+4
Under review

Integration Geninventorynumber plugin

Walid Nouh 10 years ago updated by glpi 6 years ago 2
Upgrade inventory number generation capability by integrating Geninventory plugin into GLPi's core
+3

Bussines Rules For Tickets

Guille 2 weeks ago updated 2 weeks ago 0

Currently, in each Business Rule for Tickets, we have a unique criterion that, if met, applies the defined actions when that criterion is true.


What possibility would there be to expand the number of criteria to more than one as well as the actions associated with each of them, all within the same Business Rule for Tickets?


Example for a single rule: Assignment rule according to the ticket title

Criteria #CriteriaActions if true
Criteria 1Title Contains 'printer without toner'Category Assign Change Toner
Criteria 2Title Contains 'computer does not turn on'Category Assign Technical Support
...............
Criteria NCriteria NActions N if true

This would not only simplify the number of defined rules but also allow for grouping similar criteria and actions in a single Business Rule for Tickets.

This would allow, for example, to assign service categories to tickets generated from public forms.

+3

Custom User Profile Based on Entity

glpibugreporter 9 months ago 0

It would be beneficial to create custom user profiles in GLPI based on departments and assign permissions to different entities.

(This example is very simplified)

Example:

  1. User Profiles:

    • IT Department
    • HR Department
    • Finance Department
    • Marketing Department
  2. Permissions:

    • Tickets
    • Assets
    • Projects
  3. Entities:

    • IT Entity
    • HR Entity
    • Finance Entity
    • Marketing Entity

Permission Matrix:

EntityDepartmentTicketsAssetsProjects
IT EntityITYesYesYes
FinanceYesYesYes
HRYesNoNo
MarketingYesYesYes
HR EntityHRYesNoNo
MarketingYesYesYes
Finance EntityITYesYesYes
FinanceYesYesYes
HRYesNoNo
MarketingYesYesYes
Marketing EntityMarketingYesYesYes
HRYesNoNo
ITYesYesYes

Collaborative Projects:

ProjectDepartments InvolvedEntity
Project AIT, FinanceIT Entity
Project BHR, MarketingHR Entity
Project CIT, Finance, MarketingFinance Entity
Project DMarketing, HR, ITMarketing Entity

Explanation:

  • IT Entity: IT and Finance departments collaborate on Project A.
  • HR Entity: HR and Marketing departments collaborate on Project B.
  • Finance Entity: IT, Finance, and Marketing departments collaborate on Project C.
  • Marketing Entity: Marketing, HR, and IT departments collaborate on Project D.

Benefits:

  • No need to switch profiles.
  • All information is available in one view.
  • Users see only the departments and entities where they have permissions.
  • Simplifies workflow and improves efficiency.
  • Enhances collaboration by allowing multiple departments to share permissions within the same entity.

With templates, you can set rules for defining items like tickets or assets. Applying this to profile customization in GLPI allows users to work within the full structure of the root entity but only see departments and entities where they have permissions. This avoids the need to change profiles to work in different departments.

+3

Dashboards / create widget for each "saved search"

Loiseau2nuit 10 months ago 0

When creating a dashboard, could we possibly be able to integrate "saved search" results as widgets ?
Thanks in advance

Lorsque nous créons des "tableaux de bord" (ou 'dashboard'), peut-on imaginer une possibilité d'intégrer les résultats des "recherches sauvegardées" sous forme de widgets ?
Merci par avance