Responsible for one Agent.

Moderator: crythias

Locked
spiderpig
Znuny expert
Posts: 198
Joined: 15 Dec 2011, 02:26
Znuny Version: OTRS 5

Responsible for one Agent.

Post by spiderpig »

Hi,

i was wondering if it is possible to let only one Agent(manager) have permission to control the Responsible on tickets. ?
OTRS 4.0 running on Centos 7
micshi
Znuny expert
Posts: 191
Joined: 05 Jul 2011, 16:10
Znuny Version: 3.2.2
Real Name: Micshi
Location: Beijing
Contact:

Re: Responsible for one Agent.

Post by micshi »

That may be possible, but I did not validate it.

The agents permission of OTRS is based on role. You can enable responsible permission only to the service manager and all other agents don't have responsible permission.

Thanks,

micshi
OTRS 3.2.2, ITSM 3.2.2, SystemMonitor
Ubuntu, Apache2, MySQL 5
My OTRS Blog
OTRS Basic Concept Training
OTRS Demo Instance
ferrosti
Znuny superhero
Posts: 723
Joined: 10 Oct 2007, 14:30
Znuny Version: 3.0
Location: Hamburg, Germany

Re: Responsible for one Agent.

Post by ferrosti »

You´d have to add a group, which you limit this module on in SysConfig. This way only an Agent with this group is able to see the Responsible button. Make sure to remove the Responsible feature from other Webforms, if so.
openSuSE on ESX
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
spiderpig
Znuny expert
Posts: 198
Joined: 15 Dec 2011, 02:26
Znuny Version: OTRS 5

Re: Responsible for one Agent.

Post by spiderpig »

Thank you for the reply,
change plan :)

now i want to make the manager default responsible for one queue (every ticket) do you think that is possible ?
and do i understand it right, responsible is more for managers to have overview and the agent is the worker ?
OTRS 4.0 running on Centos 7
ferrosti
Znuny superhero
Posts: 723
Joined: 10 Oct 2007, 14:30
Znuny Version: 3.0
Location: Hamburg, Germany

Re: Responsible for one Agent.

Post by ferrosti »

There is no need to bind a responsible to a queue, since by organization one can easily handle it.
Responsibility for tickets makes sense in case tickets are to be moved between queues, so that the responsible person is able to keep track of tickets/topics.

One could install a filter and set the responsible person as soon as a ticket is opened, but I won´t go for that, since vacation and off-site work would need someone else to have a look on this.
openSuSE on ESX
IT-Helpdesk: OTRS 3.0
Customer Service: OTRS 3.0 (upgraded from 2.3)
Customer Service (subsidiary): OTRS 3.0
+additional test and development systems
Locked