is the SolutionDiffInMin field store somewhere in the database? Seria For retrieval in a sql query. I know I can remove the statistical section but I'm interested for a sql query.
I need to recover this field for a sql query. I know I can take it from the statistics section but I'm interested for a sql query.
Thanks you in advance.
[SOLVED]SolutionDiffInMin in Database
Moderator: crythias
[SOLVED]SolutionDiffInMin in Database
Last edited by Gonzalo on 17 Feb 2015, 19:09, edited 1 time in total.
OTRS 5.0.8 with Oracle Linux Server release 7.1 with MariaDB database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: SolutionDiffInMin in Database
From Kernel/System/Ticket.pm:
The variables are interpreted further within the same area of Ticket.pm.
It's not trivial to pull via SQL query, because it may require additional work against working Calendar.
Code: Select all
$Data{SolutionDiffInMin} = int( ( $EscalationSolutionTime - $WorkingTime ) / 60 );
It's not trivial to pull via SQL query, because it may require additional work against working Calendar.
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
Re: SolutionDiffInMin in Database
Thanks @crythias.
I checked yesterday this file Ticket.pm when I was looking for SolutionDiffInMin through this forum and in the web.
My problem as you said is that not every SLAs are with 24x7 calendar.
Could you help me or guide how to pull via SQL query? Now we are taking this information with the ticket_history and compare unix_dates, but this works for 24x7.
Thanks in advance,
I checked yesterday this file Ticket.pm when I was looking for SolutionDiffInMin through this forum and in the web.
My problem as you said is that not every SLAs are with 24x7 calendar.
Could you help me or guide how to pull via SQL query? Now we are taking this information with the ticket_history and compare unix_dates, but this works for 24x7.
Thanks in advance,
OTRS 5.0.8 with Oracle Linux Server release 7.1 with MariaDB database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database
Re: SolutionDiffInMin in Database
you can not query calendars via SQL
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: SolutionDiffInMin in Database
Thanks,
Finally we have decided to store the "scalation_response_time" and "scalation_solution_time" ticket field in other table when the ticket is created via trigger.
We have not different scalation services, only level 1. The only problem I think is if one agent change the SLA. ¿do you see other problems?
Best regards!!!
Finally we have decided to store the "scalation_response_time" and "scalation_solution_time" ticket field in other table when the ticket is created via trigger.
We have not different scalation services, only level 1. The only problem I think is if one agent change the SLA. ¿do you see other problems?
Best regards!!!
OTRS 5.0.8 with Oracle Linux Server release 7.1 with MariaDB database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database
---------------------------------------------------------
OTRS 3.3.6 on Centos 6.0 with MySQL database