how to restrict agent to assign only himself
Moderator: crythias
-
- Znuny newbie
- Posts: 40
- Joined: 16 Mar 2011, 17:12
- Znuny Version: 3.0.6
how to restrict agent to assign only himself
Hi,
I would like to restrict an Agent to be able to only (lock = change owner to himself) and not to someone else. Is there a way to do it.
Thanks in advance
Ariel
I would like to restrict an Agent to be able to only (lock = change owner to himself) and not to someone else. Is there a way to do it.
Thanks in advance
Ariel
OTRS:ITSM 3.0.6 on Centos 5.5 with MySQL database connected to an Active Directory for Agents.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: how to restrict agent to assign only himself
Agents can only lock their own tickets...
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 40
- Joined: 16 Mar 2011, 17:12
- Znuny Version: 3.0.6
Re: how to restrict agent to assign only himself
Thanks for the reply!
Nevertheless, it is the story of the chicken and the egg:)
I would like to give the agent the possibility to pull a ticket to himself (Lock) but not to change the owner to someone else.
Is this possible?
Thanks
Ariel
Nevertheless, it is the story of the chicken and the egg:)
I would like to give the agent the possibility to pull a ticket to himself (Lock) but not to change the owner to someone else.
Is this possible?
Thanks
Ariel
OTRS:ITSM 3.0.6 on Centos 5.5 with MySQL database connected to an Active Directory for Agents.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: how to restrict agent to assign only himself
Yes. Check permissions in the group.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 40
- Joined: 16 Mar 2011, 17:12
- Znuny Version: 3.0.6
Re: how to restrict agent to assign only himself
To make the required workflow clearer:
1. Incoming tickets should be without Owner (how do I define this default?)
2. Every agent assigned to the first line support queue receives a notification.
3. One of them shall lock the ticket and start working on it.
4. If he is not able to solve it he should move it to the second level support and so on
Thanks for the help.
Ariel
1. Incoming tickets should be without Owner (how do I define this default?)
2. Every agent assigned to the first line support queue receives a notification.
3. One of them shall lock the ticket and start working on it.
4. If he is not able to solve it he should move it to the second level support and so on
Thanks for the help.
Ariel
OTRS:ITSM 3.0.6 on Centos 5.5 with MySQL database connected to an Active Directory for Agents.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: how to restrict agent to assign only himself
by default, they have no owner (or the otrs@localhost is the default owner).ArielRauch wrote:To make the required workflow clearer:
1. Incoming tickets should be without Owner (how do I define this default?)
if the agent is part of the group for "First line support queue" and has personal notification turned on and "First line support group" is in his My queues, and email works, this happens.2. Every agent assigned to the first line support queue receives a notification.
a ticket is locked when an agent clicks lock or clicks "Reply" and sends a reply to the ticket.3. One of them shall lock the ticket and start working on it.
if he is not able to solve it, he can move it to "second level support queue", but you may want to make the ticket unlocked on move to queue (sysconfig)4. If he is not able to solve it he should move it to the second level support and so on
Edit: but none of this has anything to do with the original topic.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 40
- Joined: 16 Mar 2011, 17:12
- Znuny Version: 3.0.6
Re: how to restrict agent to assign only himself
First of all thank you very much!
Your EDIT remark is right but:) I wanted the Agent to be not able to change the owner but to himself (lock) - In the meantime I found a way via the ACL rules.
Secondly as you said the default owner is otrs admin - how can I avoid this?
Thanks
Ariel
Your EDIT remark is right but:) I wanted the Agent to be not able to change the owner but to himself (lock) - In the meantime I found a way via the ACL rules.
Secondly as you said the default owner is otrs admin - how can I avoid this?
Thanks
Ariel
OTRS:ITSM 3.0.6 on Centos 5.5 with MySQL database connected to an Active Directory for Agents.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: how to restrict agent to assign only himself
Otrs@localhost is just a placeholder. If you want to rename it, you can do that through the admin user list. If you want a different default owner, that can happen via postmaster filter or generic agent. It's not practical to remove it.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 40
- Joined: 16 Mar 2011, 17:12
- Znuny Version: 3.0.6
Re: how to restrict agent to assign only himself
In the end I solved my private issue by defining ACLs that way that the owner button is not visible to the agents
Thanks
Ariel
Thanks
Ariel
OTRS:ITSM 3.0.6 on Centos 5.5 with MySQL database connected to an Active Directory for Agents.
Re: how to restrict agent to assign only himself
I have the same problem, please let me know how you resolved it. i.e how you created the acl
thanks in advance.
Kenmurimi
thanks in advance.
Kenmurimi
OTRS 2.4.7 on SUSE and on MySQL database
OTRS 3.2.10 on CentOS and MySQL database
OTRS 3.2.10 on CentOS and MySQL database
-
- Znuny newbie
- Posts: 61
- Joined: 17 Dec 2010, 13:22
- Znuny Version: 3.0
Re: how to restrict agent to assign only himself
Probably like this:
$Self->{TicketAcl}->{'ACL-Name-1'} = {
# match properties
Properties => {
# current ticket match properties
Ticket => {
Queue => ['the queue'],
}
},
# return possible options (white list)
Possible => {
# possible ticket options (white list)
Ticket => {
State => ['new', 'open', 'pending reminder'],
},
# possible action options
Action => {
AgentTicketLock => 1,
AgentTicketZoom => 1,
AgentTicketClose => 0,
AgentTicketPending => 0,
AgentTicketNote => 0,
AgentTicketHistory => 0,
AgentTicketPriority => 0,
AgentTicketFreeText => 1,
AgentTicketHistory => 0,
AgentTicketCompose => 0,
AgentTicketBounce => 0,
AgentTicketTicketPrint => 0,
AgentTicketForward => 0,
AgentLinkObject => 0,
AgentTicketPrint => 0,
AgentTicketPhone => 0,
AgentTicketCustomer => 0,
AgentTicketMerge => 0,
AgentTicketPhoneOutbound => 0,
AgentTicketOwner => 0,
},
},
};
$Self->{TicketAcl}->{'ACL-Name-1'} = {
# match properties
Properties => {
# current ticket match properties
Ticket => {
Queue => ['the queue'],
}
},
# return possible options (white list)
Possible => {
# possible ticket options (white list)
Ticket => {
State => ['new', 'open', 'pending reminder'],
},
# possible action options
Action => {
AgentTicketLock => 1,
AgentTicketZoom => 1,
AgentTicketClose => 0,
AgentTicketPending => 0,
AgentTicketNote => 0,
AgentTicketHistory => 0,
AgentTicketPriority => 0,
AgentTicketFreeText => 1,
AgentTicketHistory => 0,
AgentTicketCompose => 0,
AgentTicketBounce => 0,
AgentTicketTicketPrint => 0,
AgentTicketForward => 0,
AgentLinkObject => 0,
AgentTicketPrint => 0,
AgentTicketPhone => 0,
AgentTicketCustomer => 0,
AgentTicketMerge => 0,
AgentTicketPhoneOutbound => 0,
AgentTicketOwner => 0,
},
},
};
OTRS 3.0.7 with MySQL on Windows server 2003 r2 server with AD integration for customers.