Hi list,
We are migrating over to RT3 from Lighthouse and I figured I could simply
write a script to fill data directly into the database, rather than going
through the RT api. The reason for me doing this, is that I’m really not
very fluent in perl.
Things appear to work except for one thing - It isn’t possible to reassign
tickets. Neither through Take/Steal or through direct assignment. This is
not a permission problem, as there is no problem when we create a new
ticket in the same queue.
The error message we receive is rather cryptical, stating “Could not change
owner:” (Nothing after that colon).
I know I brought this upon myself, but does any one here have any idea
about what is wrong?
We’re running RT 3.8 on Ubuntu.
troels
I know I brought this upon myself, but does any one here have any idea
about what is wrong?
You didn’t create the internal groups RT uses for roles on a ticket,
including Owner. Running rt-validator may be able to fix this up for
you, but it’s likely to not be the only thing that’s a little odd in
your db.
Thomas
Thanks. rt-validator did indeed balk, but recreating the internal groups
didn’t solve the problem.
Anyway - As a workaround, we just created new tickets and merged the faulty
tickets into the newly created one and it appears to work.
troelsOn 25 April 2012 15:03, Thomas Sibley trs@bestpractical.com wrote:
On 04/25/2012 04:45 AM, Troels Knak-Nielsen wrote:
I know I brought this upon myself, but does any one here have any idea
about what is wrong?
You didn’t create the internal groups RT uses for roles on a ticket,
including Owner. Running rt-validator may be able to fix this up for
you, but it’s likely to not be the only thing that’s a little odd in
your db.
Thomas