Problem creating Tickets from the commandline

Hi, I am using RT 2.0.14 on Debian.

I want to create an Ticket via the commandline. If I do

./rt --create --subject=“test commandline8” --queue=19
--requestors=j.herbert@pelion12.de --noedit, the ticket gets created
fine.

What information do I need for the --keyword Parameter? My trials so far
didn’t create a Ticket with any chosen Keyword set.

Thanks in Advance,

J�rg

Hi Scott, your wrote:

./rt --create --subject=“test” --queue=19
--requestors=j.herbert@pelion12.de --noedit --keywords+colour/red

I don’t think you need an “=” after the word keywords, but you do need
the + to say “add” or the “-” to remove…

Hope that helps, just say if I’m still not clear!

I did define the Keywords and associated it with the queue as you said,
but when I do:

./rt --create --subject=“test” --queue=19 --requestors=j.herbert@pelion12.de --noedit --keywords+colour/red (Keyword-example)

rt says: Ticket 8112 created in queue ‘foo’, but the Keyword is not set. Is it possible that i have to use numeric Values here as for the queue?

Bye for now,
Bis denne,
Joerg

Hi,

I found that I also can’t insert text when creating a Ticket via the
commandline.

The Keyword are set up correct in Keywords and connected with an
Description in Queues via the Webinterface.

But if I do

dev2:/home/her# /usr/share/request-tracker/bin/rt --create
–subject=“test commandline II 1” --queue=19
--requestors=j.herbert@pelion12.de --keywords+Problemfeld/Sonstiges
–source test-ticket --debug

the Output is
No $EDITOR variable defined
Ticket 8127 created in queue ‘Test’.

and in the Webinterface I have no text from test-ticket and no Keyword
set.

The Logi shows:

[Thu Jun 19 11:03:09 2003] [warning]: Unknown option:
keywords+problemfeld/sonstiges

[Thu Jun 19 11:03:09 2003] [debug]: Creating a new ticket
[Thu Jun 19 11:03:09 2003] [crit]: No $EDITOR variable defined

[Thu Jun 19 11:03:10 2003] [warning]: Use of uninitialized value in
concatenation (.) or string at /usr/share/request-tracker/
lib/RT/Ticket.pm line 285.

[Thu Jun 19 11:03:10 2003] [warning]: RT::Ticket=HASH(0x83ec820)
->Create called with an unknown datatype for Owner: . Default
ing to Nobody.

[Thu Jun 19 11:03:10 2003] [warning]: Use of uninitialized value in join
or string at /usr/share/request-tracker/lib/RT/Ticket
.pm line 1186.

[Thu Jun 19 11:03:10 2003] [debug]: now requiring
RT::Condition::OwnerChange

[Thu Jun 19 11:03:10 2003] [debug]: RT::Transaction=HASH(0x89f3ccc):
Checking condition OnOwnerChange…

[Thu Jun 19 11:03:10 2003] [warning]: Use of uninitialized value in
string eq at /usr/share/request-tracker/lib/RT/Condition/O
wnerChange.pm line 21.

[Thu Jun 19 11:03:10 2003] [debug]: RT::Transaction=HASH(0x89f3ccc):
Doesn’t match condition OnOwnerChange…

[Thu Jun 19 11:03:10 2003] [info]: Ticket 8127 created in queue
’Test’.

What an I doing wrong?

Bye for now,
Bis denne,
Joerg

Hi, I am using RT 2.0.14 on Debian.

I want to create an Ticket via the commandline. If I do

./rt --create --subject=“test commandline8” --queue=19
--requestors=j.herbert@pelion12.de --noedit, the ticket gets created
fine.

What information do I need for the --keyword Parameter? My trials so far
didn’t create a Ticket with any chosen Keyword set.

–keywords[+|-]<keyword_select>/

An example works best. Remember you must first go to the
Configuration/Keywords area to define your keyword values. The best option
is to define them with a hierarchy that is easy to distinguish per queue,
such as /queues/nameofqueue and /queues/nameofqueue2 and so on.

For example:

/queues/foo
/queues/foo/red
/queues/foo/blue
/queues/bar
/queues/bar/red
/queues/bar/blue

You would then go to Configuration -> Queues -> foo -> Keyword Selections
and apply those values to a named selection, such as “colour”. You’d see
in the interface something like:

[ ] : (Single/Multiple) children of (entire keyword hierarchy)

Now, fill in “colour” for the value in the box, then select “Single” from
the first popup and then “/queues/foo” from the second.

Now you’ve coupled the globally defined keyword hierarchy with a named
"selection" for that queue.

You may know all this, but without doing this part the command line will
never work. You may NOW assign the keywords to a ticket by doing:

./rt --create --subject=“test” --queue=19
--requestors=j.herbert@pelion12.de --noedit --keywords+colour/red

I don’t think you need an “=” after the word keywords, but you do need the

  • to say “add” or the “-” to remove…

Hope that helps, just say if I’m still not clear!

With kind regards,

Scott

Joerg Herbert wrote:

I found that I also can’t insert text when creating a Ticket via the
commandline.

the Output is
No $EDITOR variable defined
Ticket 8127 created in queue ‘Test’.

So, what happens if you define EDITOR in your environment?
Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances

Joerg Herbert wrote:

I found that I also can’t insert text when creating a Ticket via the
commandline.

the Output is
No $EDITOR variable defined
Ticket 8127 created in queue ‘Test’.

So, what happens if you define EDITOR in your environment?

The Editor defined in $EDITOR is called. Even if I do “–source
test-ticket”, the Editor is called.

Any help would be really great.

Bye for now,
Bis denne,
Joerg

Joerg Herbert wrote:

So, what happens if you define EDITOR in your environment?

The Editor defined in $EDITOR is called. Even if I do “–source
test-ticket”, the Editor is called.

Ah, so it does what it’t supposed to? What am I missing?