Le 2011-07-28 10:55, Michiel Beijen a écrit :

Hi Ugo,

On Thu, Jul 28, 2011 at 15:58, Ugo Bellavance wrote:

...

- Have a response time associated to a priority

Only if you also select a different SLA. (this can be automated though, just did that for a customer).

So I guess that if we don't use SLAs, we can just enable it and createone SLA per priority? In fact, we don't set our response time on an SLA, we want to set it automatically only based on priority. I think your suggestion fits the need, though. Is it complex to automate it? GenericAgent? I wonder why GenericAgent can't be configured to run every minyte... or when a ticket is received...

...

- Have a "target date" assigned manually by an agent for solution for a ticket

You could use a free time field for that.

I looked at it, but I couldn't find anything about it in the admin manual. Can you provide me with a quick procedure to implement it? I'm pretty sure this is done in Core::ArticleFreeText but I'm not 100% of the meaning of the parameters.

...

With this info, would it be possible to have a report for:

- Tickets that do not meet the response time - Tickets that do not meet the solution target date

Would be possible, then, yes.

BTW we're looking for customers who'd like to start working with us on improving SLA handling; you'll get the benefit of initial involvement with the development and the possibility to define SLA's on a much deeper basis; after a while this would probably then become available in next versions of OTRS. If anyone is interested, feel free to shoot me an email.

Email sent. Thanks, Ugo

Yes, absolutely. On Thu, Jul 28, 2011 at 20:47, Ugo Bellavance wrote:

Le 2011-07-28 12:15, Ugo Bellavance a écrit :

...

Le 2011-07-28 10:55, Michiel Beijen a écrit :

...

...

...

- Have a "target date" assigned manually by an agent for solution for a ticket

You could use a free time field for that.

Could we build a response template that would include this, using ""?

Thanks,

Ugo

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Happy Friday people! I was wondering if anyone had any suggestions on how to resolve this issue... I am moving otrs to another server and during the backup process I am running into this error pg_dump: dumping contents of table article_attachment pg_dump: SQL command failed pg_dump: Error message from server: ERROR: unexpected chunk number 7 (expected 6) for toast value 77281 in pg_toast_57366 pg_dump: The command was: COPY public.article_attachment (id, article_id, filename, content_size, content_type, content, create_time, create_by, change_time, change_by, content_id, content_alternative) TO stdout; pg_dump: *** aborted because of error I have tried a vacuum and reindex with no successes. Mik Rose

Its a postgresdb. Is there a similar method for postgres? Mik Rose | Director, IT - Support Services | PowerSoft Development Corp 1 (250) 642-0295 x23 http://www.power-soft.com Live Support This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. On 2011-08-19, at 11:36 AM, Carlos Andrés Gallego Arboleda wrote:

if you dont stop the mysql during the data copy, maybe the DB is corrupted.

use this command.

mysqlcheck --repair -p otrs

Regards.

2011/8/19 Mik Rose Happy Friday people!

I was wondering if anyone had any suggestions on how to resolve this issue... I am moving otrs to another server and during the backup process I am running into this error pg_dump: dumping contents of table article_attachment

pg_dump: SQL command failed pg_dump: Error message from server: ERROR: unexpected chunk number 7 (expected 6) for toast value 77281 in pg_toast_57366

pg_dump: The command was: COPY public.article_attachment (id, article_id, filename, content_size, content_type, content, create_time, create_by, change_time, change_by, content_id, content_alternative) TO stdout;

pg_dump: *** aborted because of error

I have tried a vacuum and reindex with no successes.

Mik Rose

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Hi Steve, Don't know if there is a way to fix that table, but you might not be too concerned. This table holds attachments that customers and agents attach to ticket articles. You might consider storing that in the filesystem instead of the database ("there's a sysconf setting for that" should be the new OTRS motto...) and just discard the contents of that table in the migration. Yes, tickets will lose attachments, but maybe everybody can live with that. Lars From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Steve Clark Sent: Friday, August 19, 2011 8:54 PM To: User questions and discussions about OTRS. Subject: Re: [otrs] DATA Corruption On 08/19/2011 02:37 PM, Mik Rose wrote: Its a postgresdb. Is there a similar method for postgres? Mik Rose | Director, IT - Support Services | PowerSoft Development Corp 1 (250) 642-0295 x23 http://www.power-soft.comhttp://www.power-soft.com/ Live Supporthttps://secure.logmeinrescue.com/Customer/Download.aspx?EntryID=15095831 This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. On 2011-08-19, at 11:36 AM, Carlos Andrés Gallego Arboleda wrote: if you dont stop the mysql during the data copy, maybe the DB is corrupted. use this command. mysqlcheck --repair -p otrs Regards. 2011/8/19 Mik Rose mailto:mrose@power-soft.com> Happy Friday people! I was wondering if anyone had any suggestions on how to resolve this issue... I am moving otrs to another server and during the backup process I am running into this error pg_dump: dumping contents of table article_attachment pg_dump: SQL command failed pg_dump: Error message from server: ERROR: unexpected chunk number 7 (expected 6) for toast value 77281 in pg_toast_57366 pg_dump: The command was: COPY public.article_attachment (id, article_id, filename, content_size, content_type, content, create_time, create_by, change_time, change_by, content_id, content_alternative) TO stdout; pg_dump: *** aborted because of error I have tried a vacuum and reindex with no successes. You would be better off posting this to the postgresql-users list. -- Stephen Clark NetWolves Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@netwolves.commailto:steve.clark@netwolves.com http://www.netwolves.com