Rt CLI 'priority' bug?

RT Users
1

Using
./rt --create --status=new --queue=1 --owner=2 --subject=“test”
–priority=1 …

the priority field is blank when the ticket is created.
I found in the database there are these fields
Priority
InitialPriority
FinalPriority

and that when I use the CLI the InitialPriority and Priority fields are
both blank. But when I use the WebUI these fields are populated. So on
a hunch I modified rt, in the section

{{{ Check if we’re creating, if so, create the ticket and be done

I modified the line
Priority => $priority,
to be
InitialPriority => $priority,

and this fixed the problem. Don’t know if I stumbled across a bug or
not, but thought I would let Jesse and others know in case it is.
-Fred

2

Thanks. this will be fixed in 2.0.10.On Mon, Nov 26, 2001 at 10:00:56AM -0600, Percynski, Fred wrote:

Using
./rt --create --status=new --queue=1 --owner=2 --subject=“test”
–priority=1 …

the priority field is blank when the ticket is created.
I found in the database there are these fields
Priority
InitialPriority
FinalPriority

and that when I use the CLI the InitialPriority and Priority fields are
both blank. But when I use the WebUI these fields are populated. So on
a hunch I modified rt, in the section

{{{ Check if we’re creating, if so, create the ticket and be done

I modified the line
Priority => $priority,
to be
InitialPriority => $priority,

and this fixed the problem. Don’t know if I stumbled across a bug or
not, but thought I would let Jesse and others know in case it is.
-Fred

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.