Change Ticket Type upon reply
Moderator: crythias
-
- Znuny newbie
- Posts: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Change Ticket Type upon reply
Ive noticed its possible to force an agent to provide a TicketType if they close a ticket by enabling this setting Ticket::Frontend::AgentTicketClose###TicketType = Yes
I was wondering if there is not a way to force the agents to select a TicketType upon replying on the ticket.
eg: Ticket::Frontend::AgentTicketReply###TicketType
I know you can change it under "Additional ITSM Fields" but I need to force my agents to choose a Type.
Really hope this is available.
Regards
I was wondering if there is not a way to force the agents to select a TicketType upon replying on the ticket.
eg: Ticket::Frontend::AgentTicketReply###TicketType
I know you can change it under "Additional ITSM Fields" but I need to force my agents to choose a Type.
Really hope this is available.
Regards
OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0
-
- Moderator
- Posts: 644
- Joined: 19 Jun 2007, 17:11
- Znuny Version: various
- Real Name: Daniel Obée
- Location: Berlin
Re: Change Ticket Type upon reply
You could alter the .dtl to not set the given ticketType as default. Since Type is a mandatory field this should do the trick.
Greets
Dan
Greets
Dan
-
- Znuny newbie
- Posts: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Re: Change Ticket Type upon reply
Thanks for the prompt response.
Can you please be more specific where this .dtl can be located
Your help is greatly appreciated

Can you please be more specific where this .dtl can be located
Your help is greatly appreciated

OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0
-
- Znuny superhero
- Posts: 723
- Joined: 10 Oct 2007, 14:30
- Znuny Version: 3.0
- Location: Hamburg, Germany
Re: Change Ticket Type upon reply
$OTRS_HOME/Kernel/Output/HTML/Standard
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
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
-
- Znuny newbie
- Posts: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Re: Change Ticket Type upon reply
This DTL is new to me, and Im still not sure what to do.
Do I have to look at the AgentTicketActionCommon.dtl or AgentTicketCompose.dtl?
Im still not sure what I should do?
Many thanks
Do I have to look at the AgentTicketActionCommon.dtl or AgentTicketCompose.dtl?
Im still not sure what I should do?
Many thanks
OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0
-
- Znuny newbie
- Posts: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Re: Change Ticket Type upon reply
Hi.
Your assistance will be greatly appreciated . I'm still sitting with this issue.
thanks
Your assistance will be greatly appreciated . I'm still sitting with this issue.
thanks
OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Change Ticket Type upon reply
Yes, Daniel/tisar has the right idea.
First determine the screen you're on, then edit the accompanying dtl file. you might put a javascript assigning TypeId value to "" or "-" or whatever "-" is supposed to be, but then again, if you are so reliant on ticket Type, perhaps you might rethink whether you need it vs a queue designation.
First determine the screen you're on, then edit the accompanying dtl file. you might put a javascript assigning TypeId value to "" or "-" or whatever "-" is supposed to be, but then again, if you are so reliant on ticket Type, perhaps you might rethink whether you need it vs a queue designation.
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: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Re: Change Ticket Type upon reply
If I look at the template page AgentTicketActionCommon.dtl, the code below is used to display the type field when an Agent Closes a Ticket.
Now If I Copy the abovementioned Code in the AgentTicketCompose.dtl ,which is the template that is being used when an Agent Replies, Nothing happens.
Am I missing something here? *blush*
I currently have one queue, but would like to break the type of queries up into categories for reporting purposes.
Code: Select all
<!-- dtl:block:Type -->
<label class="Mandatory" for="TypeID"><span class="Marker">*</span>$Text{"Type"}:</label>
<div class="Field">
$Data{"TypeStrg"}
<div id="TypeIDError" class="TooltipErrorMessage"><p>$Text{"This field is required."}</p></div>
<div id="TypeIDServerError" class="TooltipErrorMessage"><p>$Text{"This field is required."}</p></div>
</div>
<div class="Clear"></div>
<!-- dtl:block:Type -->
Am I missing something here? *blush*
I currently have one queue, but would like to break the type of queries up into categories for reporting purposes.
OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Change Ticket Type upon reply
See, that's why multiple queues are as useful as types.
Queues are, as I've explained it, categories of tickets that allow agents who are able to answer those tickets to be a part of the group for that queue.
So, if the Queue is called ChangeMe (or Raw), you can have a Queue called "Maintenance" or "Printing" or "Maintenance" with a subqueue of "Electrical" (Maintenance::Electrical).
but even if the type is mandatory, if it's already chosen (default), making the field mandatory won't make any difference, because it's already filled, so you *must* make the Type field invalid on load of the form, in order for it to be mandatory to be changed.
Queues are, as I've explained it, categories of tickets that allow agents who are able to answer those tickets to be a part of the group for that queue.
So, if the Queue is called ChangeMe (or Raw), you can have a Queue called "Maintenance" or "Printing" or "Maintenance" with a subqueue of "Electrical" (Maintenance::Electrical).
but even if the type is mandatory, if it's already chosen (default), making the field mandatory won't make any difference, because it's already filled, so you *must* make the Type field invalid on load of the form, in order for it to be mandatory to be changed.
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: 10
- Joined: 08 Jun 2011, 12:22
- Znuny Version: 3.07
- Real Name: Reynold Woeke
Re: Change Ticket Type upon reply
Thanks, Ive now looked at rather using the sub-queues and it will work for Us.
I come out of an environment where we worked with one queue that is categorized per type. This approach will work just as well.
I come out of an environment where we worked with one queue that is categorized per type. This approach will work just as well.
OTRS 3.07 - Windows 2003 with LDAP for Agents
OTRS FANBOY 2.0
OTRS FANBOY 2.0