Hello,
We are dealing with Level1 support managed internaly and Level 2 and 3 with contractors.
SLA are based on ticket creation so we cannot use them to check SLA negotiated with contractors; otherwise we could reset SLA when moving the ticket to the contractor queue. But this not an option in OTRS.
So my solution would be:
1 - set a date dynamic field ReferenceDate when we move the ticket to the contractor Queue. This will be the reference date/time for contractors activity.
2 - based on SLAs or by code calculate the DueDate. The calculation must take into account the working hours of OTRS calendar defined.
My questions are the following:
1 - can we set the value of a fields on ticket move to a specifc queue?
2 - Is there an existing function to calculate Duedate based on SLA? and based on calendar working hour? maybe an SQL function like standard dateadd?
Custom DueDate based on calendar
Moderator: crythias
-
- Administrator
- Posts: 4253
- Joined: 18 Dec 2007, 12:23
- Znuny Version: Znuny and Znuny LTS
- Real Name: Roy Kaldung
- Company: Znuny
- Contact:
Re: Custom DueDate based on calendar
This needs custom development of an event module.
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
Use a test system - always.
Do you need professional services? Check out https://www.znuny.com/
Do you want to contribute or want to know where it goes ?
Re: Custom DueDate based on calendar
Ok so we decided to use the split function.
So that when I need to send ticket to contractors it create a copy of existing ticket with SLA reset.
Is there a way to close parent ticket on child close or at least inform parent owner that child is closed?
Shall we better use master slave module?
So that when I need to send ticket to contractors it create a copy of existing ticket with SLA reset.
Is there a way to close parent ticket on child close or at least inform parent owner that child is closed?
Shall we better use master slave module?