A small change maybe


#1

You sort of use ‘serial’ ‘transaction’ ‘request’ number interchangibly.

It would be nice if it was called one thing.

I like transaction number instead of serial number as is displayed
in the interface. It might make ‘merging’ a little clearer.

Thanks

Stephen Hauskins

PS- Great package.


#2

You sort of use ‘serial’ ‘transaction’ ‘request’ number interchangibly.

It would be nice if it was called one thing.

In RT2, we use ticket id and transaction id throughout.

I like transaction number instead of serial number as is displayed
in the interface. It might make ‘merging’ a little clearer.

Huh?

Thanks

Stephen Hauskins

PS- Great package.


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

jesse reed vincent – jrvincent@wesleyan.edujesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
that’s security the same way that asking for directions to topeka and
being told that a seal is a mammal is informative
-robin@apocalypse.org


#3

You sort of use ‘serial’ ‘transaction’ ‘request’ number interchangibly.

It would be nice if it was called one thing.

I like transaction number instead of serial number as is displayed
in the interface. It might make ‘merging’ a little clearer.

That might introduce more confusion - each request comprises lots of
transactions…

Charlie Brady
Aurema Pty Ltd
PO Box 305, Strawberry Hills, NSW 2012, Australia
Email:charlieb@aurema.com, Tel: +61 2 9698 2322, Fax: +61 2 9699 9174
"I think it would be a good idea." Gandhi, on Western Civilisation.


#4

You sort of use ‘serial’ ‘transaction’ ‘request’ number interchangibly.

The transaction ID is individual for each transaction. There can be
several transactions for each request. “Serial number” is the "official"
notation of a request ID in 1.0. In 2.0, we will use “Ticket ID”
(right, Jesse?).

Tobias Brox
aka TobiX
+47 22 925 871