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

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

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

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.

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:

Collaborative Projects:

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.

When using a ticket, I want to assign some consumables to it and have them be adjusted in the consumables panel.

So, if I have a printer that the team submitted a ticket for more ink, 

1. I go into the ticket
2. click a new "consumables" tab
3. Add the consumables to the ticket (just like items, only with the extra "consumables" data like who it's assigned to)
4. The inventory in consumables changes to reflect the ink that was used.