@otrs.org
Subject: [otrs] Ticket History
Hello Nick,
Ticket-id is the OTRS internal id for a ticket and Ticket-Number is the
number of the ticket which an agent will see in the dashboard per example.
Ticket-ID will be seen as well in a notification e-mail, the included URL in
this e-mail will show
Hello Nick,
Ticket-id is the OTRS internal id for a ticket and Ticket-Number is the
number of the ticket which an agent will see in the dashboard per example.
Ticket-ID will be seen as well in a notification e-mail, the included URL in
this e-mail will show at the end the internal Ticket-ID.
If y
Hi,
1) TicketID != TicketNumber . You can get the TicketID via the URL, you
can see in the browser. Open the ticket and you should see something
like "Action=AgentTicketZoom;TicketID=..."
2) Maybe the agent didn't move the ticket himself/herself, but did an
action that triggered an event module or
On 8/20/2015 1:27 PM, jan.dre...@bertelsmann.de wrote:
Hi.
Am 20.08.2015 um 18:55 schrieb Nick Bright :
Is there any more detail for ticket history available in the database that
might not be in the UI?
I have a ticket which had its' ownership changed, and moved to another queue.
The Agent
Hi.
> Am 20.08.2015 um 18:55 schrieb Nick Bright :
>
> Is there any more detail for ticket history available in the database that
> might not be in the UI?
>
> I have a ticket which had its' ownership changed, and moved to another queue.
>
> The Agent whom the action was logged under states th
Is there any more detail for ticket history available in the database
that might not be in the UI?
I have a ticket which had its' ownership changed, and moved to another
queue.
The Agent whom the action was logged under states that they didn't take
the action, and all other queried employees
size.
Live and learn.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Jason B. Loven
Sent: Thursday, March 01, 2007 12:36 PM
To: User questions and discussions about OTRS.org
Subject: [otrs] Ticket history table size revisited
I had mentione
I had mentioned a while back that I had hit a limit in MySQL with the
tablesize on my ticket_history table. I was able to get around it by
adjusting the table parameters. More of a concern is that the table hit
the limit at all. We process about 20-30 tickets a day and have been
using the system fo
day, February 08, 2007 8:57 AM
To: User questions and discussions about OTRS.org
Subject: Re: Database pruning (was: RE: [otrs] Ticket history table full
error)
Jason B. Loven wrote:
> Is there a quick way to tell?
You could for instance run an SQL query like this:
SELECT COUNT(*
Jason B. Loven wrote:
Is there a quick way to tell?
You could for instance run an SQL query like this:
SELECT COUNT(*) FROM otrs.ticket;
Nils Breunese.
PGP.sig
Description: Dit deel van het bericht is digitaal ondertekend
___
OTRS mailing lis
uning (was: RE: [otrs] Ticket history table full
error)
OK... I bit the bullet and did the max_rows change and all seems well.
Next question: Is there a way to prune the database or to archive
history out of the database to get things down in size? My history file
is currently at 4GB aft
How many tickets do you have?
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Jason B. Loven
Sent: Wednesday, February 07, 2007 11:19 AM
To: User questions and discussions about OTRS.org
Subject: Database pruning (was: RE: [otrs] Ticket history table full error
User questions and discussions about OTRS.org
Subject: [otrs] Ticket history table full error
Anyone know how to fix this? We're running 2.0.4 and I saw this showing
up in the cron logs. I've disabled cron for now but obviously that's bad
because now we're having to manually
Anyone know how to fix this? We're running 2.0.4 and I saw this showing
up in the cron logs. I've disabled cron for now but obviously that's bad
because now we're having to manually handle the incoming mail queue for
our support.
Here's the error...
DBD::mysql::db do failed: The table 'tick
14 matches
Mail list logo
