On 7/18/06, Barry L. Kline <[EMAIL PROTECTED]> wrote:
I certainly hope this is a bug. Purposefully vaporizing request numbers would be a very undesirable design decision as far as I'm concerned. I much prefer being able to type in either request number and be redirected as required.
Still on 3.4.4 right now. Waiting for things like this to shake out before upgrading.
That is my EXACT problem. We have some queues where the admins get
paged with a ticket. Let's say that ticket #200 is created and the
admins get paged. One of them decides that 200 needs to be merged into
100 (for whatever reason). The other admins look at the queue, can't
find 200 anymore and have no idea what happened to it. Was it deleted?
Was it merged? All they end up doing it wasting time trying to find
200.
I suppose I could write a scrip to send a notification when a ticket is
merged, but then I'd have to listen to the complaints of excessive pages.
Oh well, you win some and you lose some.
Barry
I certainly hope this is a bug. Purposefully vaporizing request numbers would be a very undesirable design decision as far as I'm concerned. I much prefer being able to type in either request number and be redirected as required.
Still on 3.4.4 right now. Waiting for things like this to shake out before upgrading.
--
-Tim
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com We're hiring! Come hack Perl for Best Practical: http://bestpractical.com/about/jobs.html
