Archives of closed calls

RT Developers
1

We are using the Request Tracker version 1.0.7., it’s pretty good. But we have some clarifications.

  1. How do we get the Archives of closed calls. At present once the a call is closed it’s getting removed from the list. do we need to configure anything to retain the closed calls.

Regards,
Rajeesh Kumar M.P
System Administrator,
Aalayance E-Com Services Pvt Ltd,
26/1 24 th Main, 5th Phase,
JP Nagar,
Bangalore - 560078
Phone - 2995692
Mobile - 98451-75794

2

RT 1.0.7 is OUT-OF-DATE, current version is 2.0.11, upgrade ASAP! It’s
well worth it.

A.On Thu, 3 Jan 2002, Rajeesh Kumar wrote:

We are using the Request Tracker version 1.0.7., it’s pretty good. But we have some clarifications.

  1. How do we get the Archives of closed calls. At present once the a call is closed it’s getting removed from the list. do we need to configure anything to retain the closed calls.

Regards,
Rajeesh Kumar M.P
System Administrator,
Aalayance E-Com Services Pvt Ltd,
26/1 24 th Main, 5th Phase,
JP Nagar,
Bangalore - 560078
Phone - 2995692
Mobile - 98451-75794

3

Alesh> RT 1.0.7 is OUT-OF-DATE, current version is 2.0.11, upgrade
Alesh> ASAP! It’s well worth it.

And I’m not convinced that 2.0 is ready yet either. I want to
upgrade, but it’s not a simple process when you have to keep upgrading
large parts of your web server and it’s infrastructure to do so. In
some ways I wish we didn’t have to tie so closely to Apache to get the
performance, since it’s hard to make sure that I don’t break other
things when I do upgrade.

John
John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
stoffel@lucent.com - http://www.lucent.com - 978-952-7548

4

And I’m not convinced that 2.0 is ready yet either. I want to
upgrade, but it’s not a simple process when you have to keep upgrading
large parts of your web server and it’s infrastructure to do so. In
some ways I wish we didn’t have to tie so closely to Apache to get the
performance, since it’s hard to make sure that I don’t break other
things when I do upgrade.

You could run RT’s fastcgi handler instead of using mod_perl. I’ve had
reports that it’s faster and uses less memory.

John
John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
stoffel@lucent.com - http://www.lucent.com - 978-952-7548

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

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

5

RT 2.x is way ahead of RT 1.x in any ways (stability, performance,
modifications, extensibility, etc.). It’s been ready, for a long time now.

If you’re doing a really big upgrade, then it’s normal to first test-out
the new version on a non-production server. Test the upgrade, test if
anything breaks when re-compiling apache and perl.

Regards,
AleshOn Sat, 5 Jan 2002, John Stoffel wrote:

Alesh> RT 1.0.7 is OUT-OF-DATE, current version is 2.0.11, upgrade
Alesh> ASAP! It’s well worth it.

And I’m not convinced that 2.0 is ready yet either. I want to
upgrade, but it’s not a simple process when you have to keep upgrading
large parts of your web server and it’s infrastructure to do so. In
some ways I wish we didn’t have to tie so closely to Apache to get the
performance, since it’s hard to make sure that I don’t break other
things when I do upgrade.

John
John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
stoffel@lucent.com - http://www.lucent.com - 978-952-7548