hi all?
I want my closed tickets to be read only. i.e once a ticket has been closed then it will not be possible to add any followups or even change queues by the agents.
thanks in advance.
closed tickets to be ro. [SOLVED]
Moderator: crythias
closed tickets to be ro. [SOLVED]
Last edited by kenmurimi on 10 Aug 2010, 08:57, edited 2 times in total.
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
Re: closed tickets to be ro.
I think, you can configure this option in Queue setup:
Peter
Peter
OTRS 2.4.7 with ITSM 2.0.3. running on Linux Fedora 12
Re: closed tickets to be ro.
thanks a lot Peter. is there a way i can make it ro for agents since for this i realize its only working for customers?
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
-
- Moderator
- Posts: 10169
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: closed tickets to be ro.
I think followup is not good. I think it means no tickets can have followups
Config Options: Ticket -> Core::PostMaster
PostmasterFollowUpStateClosed:
The state if a ticket got a follow-up and the ticket was already closed.
Set that to closed and it will keep the ticket closed.
But you can't keep tickets read only. And why would it be necessary? You have history on a ticket.
Config Options: Ticket -> Core::PostMaster
PostmasterFollowUpStateClosed:
The state if a ticket got a follow-up and the ticket was already closed.
Set that to closed and it will keep the ticket closed.
But you can't keep tickets read only. And why would it be necessary? You have history on a ticket.
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
-
- Moderator
- Posts: 644
- Joined: 19 Jun 2007, 17:11
- Znuny Version: various
- Real Name: Daniel Obée
- Location: Berlin
Re: closed tickets to be ro.
You can use Ticket ACLs for this: http://faq.otrs.org/otrs/public.pl?Acti ... &ItemID=68kenmurimi wrote:thanks a lot Peter. is there a way i can make it ro for agents since for this i realize its only working for customers?
Greets
Daniel
Re: closed tickets to be ro.
peter_sk: thanks alot that made it possible have the tickets ro for customers.
Crythias : I dont want the the tickets edited once closed this is because for my case the customers are to close the tickets themselves once set to resolved by the Agents. i want then to create a new tickets instead. in my case a newticket=money so once they have closed one, next time they get a similar problem they don't take the advantage of reopening a similar ticket but create a newone. i have used acl and its working perfectly
Tisar: thanks a million it worked perfectly without any hustle.
below is the Acl i have used,
$Self->{TicketAcl}->{'ACL-Name-1'} = {
Properties => {
Ticket => {
State => ['closed successful'],
}
},
Possible => {
Action => {
AgentTicketLock => 0,
AgentTicketZoom => 1,
AgentTicketClose => 0,
AgentTicketPending => 0,
AgentTicketNote => 0,
AgentTicketMove => 0,
AgentTicketHistory => 1,
AgentTicketPriority => 0,
AgentTicketFreeText => 0,
AgentTicketCompose => 0,
AgentTicketBounce => 0,
AgentTicketForward => 0,
AgentTicketTicketLink => 0,
AgentTicketPrint => 1,
AgentTicketCustomer => 1,
AgentTicketOwner => 0,
},
},
};
Crythias : I dont want the the tickets edited once closed this is because for my case the customers are to close the tickets themselves once set to resolved by the Agents. i want then to create a new tickets instead. in my case a newticket=money so once they have closed one, next time they get a similar problem they don't take the advantage of reopening a similar ticket but create a newone. i have used acl and its working perfectly
Tisar: thanks a million it worked perfectly without any hustle.
below is the Acl i have used,
$Self->{TicketAcl}->{'ACL-Name-1'} = {
Properties => {
Ticket => {
State => ['closed successful'],
}
},
Possible => {
Action => {
AgentTicketLock => 0,
AgentTicketZoom => 1,
AgentTicketClose => 0,
AgentTicketPending => 0,
AgentTicketNote => 0,
AgentTicketMove => 0,
AgentTicketHistory => 1,
AgentTicketPriority => 0,
AgentTicketFreeText => 0,
AgentTicketCompose => 0,
AgentTicketBounce => 0,
AgentTicketForward => 0,
AgentTicketTicketLink => 0,
AgentTicketPrint => 1,
AgentTicketCustomer => 1,
AgentTicketOwner => 0,
},
},
};
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