Ability to store an external reference to a ticket in another ticket system (for example a ticket opened in a bug tracker and pushed into GLPi using the webservice).

Store :

• URL
• ID
• Title

- Add a filter for "To Do" tasks would be nice

- Increase contrast of selected filter(s). Actually, it's really difficult to see which filters are selected (see screenshot).

In the screenshot, task filter has been selected.

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.

Today, when you have a root entity and several child entities, whenever you add any item to the child entities, it ends up being shared with all of them. However, there should be an option to create an exception. Currently, you are forced to share with al