Two Major Issues with OTRS configuration..Help !
Moderator: crythias
Two Major Issues with OTRS configuration..Help !
Hi Cynthias,
I am really glad that I finally found someone who could help me on the below said issues. I am creating this post after spending hours on OTRS HUB for an answer. Please suggest a solution for the below mentioned issues.
1 . Escalation times vanish after we close a ticket. Reports do not show escalated times. Only current escalated tickets are bieng shown in statistics.
2 . I have a IT service Desk Queue with three different sub queues. I also have a separate queue for situations like "approvals required" and "Procurement"(also names for two different queues). I am using the Service based SLA instead of the queue based SLA. Now that we do not have a SLA suspend feature on the open source version of the ITSM. All tickets going into procurement or Approvals queue need to have a different SLA. Should I use a service based SLA or a queue based Sla. If I am using a service based SLA my logic is that i will not have proper Statistics when I pull out data to understand the number of issues that came in over a period of time with that specific service. Please suggest the best way to go ahead.
I would also know if a service with an SLA is attached to a ticket and is moved to a queue with specific SLA's - which Sla will be effective and when we move the ticket back to the original queue it came from- which SLA is considered
I am really glad that I finally found someone who could help me on the below said issues. I am creating this post after spending hours on OTRS HUB for an answer. Please suggest a solution for the below mentioned issues.
1 . Escalation times vanish after we close a ticket. Reports do not show escalated times. Only current escalated tickets are bieng shown in statistics.
2 . I have a IT service Desk Queue with three different sub queues. I also have a separate queue for situations like "approvals required" and "Procurement"(also names for two different queues). I am using the Service based SLA instead of the queue based SLA. Now that we do not have a SLA suspend feature on the open source version of the ITSM. All tickets going into procurement or Approvals queue need to have a different SLA. Should I use a service based SLA or a queue based Sla. If I am using a service based SLA my logic is that i will not have proper Statistics when I pull out data to understand the number of issues that came in over a period of time with that specific service. Please suggest the best way to go ahead.
I would also know if a service with an SLA is attached to a ticket and is moved to a queue with specific SLA's - which Sla will be effective and when we move the ticket back to the original queue it came from- which SLA is considered
Re: Two Major Issues with OTRS configuration..Help !
My Current Version is OTRS 3.1.9 with ITSM 3.1.6
Re: Two Major Issues with OTRS configuration..Help !
Reporting: Use ticket list
"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: Two Major Issues with OTRS configuration..Help !
Please help me with the QUEUE vs Service based SLA as mentioned above
-
- Moderator
- Posts: 10169
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Two Major Issues with OTRS configuration..Help !
My understanding is that service SLA wins.
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: Two Major Issues with OTRS configuration..Help !
Cynthias,
To avoid all this can we pause Sla on OTRS ??
To avoid all this can we pause Sla on OTRS ??
-
- Moderator
- Posts: 10169
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Two Major Issues with OTRS configuration..Help !
No.
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: Two Major Issues with OTRS configuration..Help !
Like said in the above post i have tried using ticket accumulkation in reports and have escalated tickets for the past one month according to the report....however in reality I have 75 escalated tickets in otrs..please help on the same.
Re: Two Major Issues with OTRS configuration..Help !
Hi Cynthias,
Reports are a major concern with my setup now. Can you please let me know how to pull reports for closed tickets.
I have created a new state called reopen.
Whenever a user replies to a closed ticket it goes into the reopen state after which the agent checks it resolves it and closes the ticket.
However such tickets are not bieng shown in statistics.
I am using Reopen as the parameter on X - axis and agent and sla on Y - axis.
Also restricting the report for the required time period in restrictions.
Please assist.
Reports are a major concern with my setup now. Can you please let me know how to pull reports for closed tickets.
I have created a new state called reopen.
Whenever a user replies to a closed ticket it goes into the reopen state after which the agent checks it resolves it and closes the ticket.
However such tickets are not bieng shown in statistics.
I am using Reopen as the parameter on X - axis and agent and sla on Y - axis.
Also restricting the report for the required time period in restrictions.
Please assist.
-
- Moderator
- Posts: 10169
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Two Major Issues with OTRS configuration..Help !
Reports aren't my specialty, and I'm not a Cynthia. :)
I can't tell you what to do with this. Either the reply extends the duration of the ticket or it should be set to open a new ticket. (Queue settings, followup new ticket).kvytla wrote:Whenever a user replies to a closed ticket it goes into the reopen state after which the agent checks it resolves it and closes the ticket.
It's not my area of expertise, sorry.kvytla wrote:However such tickets are not bieng shown in statistics.
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