Altering status and corresponding with Jumbo page

(I’ve been blind when reading the buglist before. If this is already
documented please point me to the bug. If it’s fixed, even better)

We noticed earlier this week that RT2.0.8_02 is reopening a ticket if you

  • set the status to resolved in Jumbo->Modify ticket

AND

  • correspond with the requestor in Jumbo->Update ticket.

It looks like RT is doing the updates out of order (setting the status
to resolved, updating the transaction table with the correspondence, and
then reopening the ticket because of the correspondence). I think it should
be updating the transaction with the correspondence and then doing the
status update.

Bug? Feature?

Travis
Travis Campbell - Unix Systems Administrator = travis@beast.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@beast.amd.com
"Does anything work as expected?" Yes. An axe through the CPU.

That’s been fixed. I believe in 2.0.9.On Wed, Jan 02, 2002 at 04:03:50PM -0600, Travis Campbell wrote:

(I’ve been blind when reading the buglist before. If this is already
documented please point me to the bug. If it’s fixed, even better)

We noticed earlier this week that RT2.0.8_02 is reopening a ticket if you

  • set the status to resolved in Jumbo->Modify ticket

AND

  • correspond with the requestor in Jumbo->Update ticket.

It looks like RT is doing the updates out of order (setting the status
to resolved, updating the transaction table with the correspondence, and
then reopening the ticket because of the correspondence). I think it should
be updating the transaction with the correspondence and then doing the
status update.

Bug? Feature?

Travis

Travis Campbell - Unix Systems Administrator = travis@beast.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@beast.amd.com

  "Does anything work as expected?"  Yes.  An axe through the CPU.

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

That’s been fixed. I believe in 2.0.9.

Was this a fix to ModifyAll.html or something deeper in the RT::*
module structure? If the former, I’ll just download a 2.0.9 tarball and
diff the content of the mason files. If the latter, I’ll just live with
the bug; can’t upgrade to anything later than 2.0.8_02 without qualifying
it for the environment.> On Wed, Jan 02, 2002 at 04:03:50PM -0600, Travis Campbell wrote:

It looks like RT is doing the updates out of order (setting the status
to resolved, updating the transaction table with the correspondence, and
then reopening the ticket because of the correspondence). I think it should
be updating the transaction with the correspondence and then doing the
status update.

Thanks,
Travis
Travis Campbell - Unix Systems Administrator = travis@beast.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@beast.amd.com
"Does anything work as expected?" Yes. An axe through the CPU.

IIRC it was in Ticket.pmOn Wed, Jan 02, 2002 at 04:59:31PM -0600, Travis Campbell wrote:

On Wed, Jan 02, 2002 at 05:07:00PM -0500, Jesse Vincent wrote:

That’s been fixed. I believe in 2.0.9.

Was this a fix to ModifyAll.html or something deeper in the RT::*
module structure? If the former, I’ll just download a 2.0.9 tarball and
diff the content of the mason files. If the latter, I’ll just live with
the bug; can’t upgrade to anything later than 2.0.8_02 without qualifying
it for the environment.

On Wed, Jan 02, 2002 at 04:03:50PM -0600, Travis Campbell wrote:

It looks like RT is doing the updates out of order (setting the status
to resolved, updating the transaction table with the correspondence, and
then reopening the ticket because of the correspondence). I think it should
be updating the transaction with the correspondence and then doing the
status update.

Thanks,
Travis

Travis Campbell - Unix Systems Administrator = travis@beast.amd.com
5900 E. Ben White Blvd, Austin, TX 78741 = travis.campbell@amd.com
TEL: (512) 602-1888 PAG: (512) 604-0341 = webmaster@beast.amd.com

  "Does anything work as expected?"  Yes.  An axe through the CPU.

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.