Hello,
I understand how to set up default values for a field using a custom scrip.
However, it seems a bit odd to me to load a ticket with no value, and then
set it only if the person opening a ticket doesn’t select a value. I’d like
to set the value in the UI for a new ticket, so that it is clear to the
person opening a ticket that the value has already been set.
Does anyone know of a way to set the default values so that they are
visible when the page actually loads for a new ticket? I understand that it
may not be possible with a scrip, but I appreciate your suggestions.
Thanks,
Jim
JavaScript’s ‘onPageLoad’ is the first thing that comes to my mind, although I don’t know right off hand how you could incorporate it with the RT API in Mason. I am sure there is a way to set it with javascript or another language for when the ticket page initially loads.From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jim Lesinski
Sent: Tuesday, November 08, 2011 2:12 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Can you set default values on page load,so you can see them in a new ticket?
Hello,
I understand how to set up default values for a field using a custom scrip. However, it seems a bit odd to me to load a ticket with no value, and then set it only if the person opening a ticket doesn’t select a value. I’d like to set the value in the UI for a new ticket, so that it is clear to the person opening a ticket that the value has already been set.
Does anyone know of a way to set the default values so that they are visible when the page actually loads for a new ticket? I understand that it may not be possible with a scrip, but I appreciate your suggestions.
Thanks,
Jim
I understand how to set up default values for a field using a custom scrip. However, it seems
a bit odd to me to load a ticket with no value, and then set it only if the person opening a
ticket doesn’t select a value. I’d like to set the value in the UI for a new ticket, so that
it is clear to the person opening a ticket that the value has already been set.
Does anyone know of a way to set the default values so that they are visible when the page
actually loads for a new ticket? I understand that it may not be possible with a scrip, but I
appreciate your suggestions.
RT-Extension-QuickCalls gives you a series of quick pre-filled ticket
Create links on your homepage. This and may give you some ideas on how
to do it.
-kevin
It looks like RT-Extension-QuickCalls can set some values using querystring
parameters, but that doesn’t seem to be working for custom fields. Is it
even possible to set values for custom fields using querystring params? If
you can, I may be able to use that.On Tue, Nov 8, 2011 at 3:17 PM, Kevin Falcone falcone@bestpractical.comwrote:
On Tue, Nov 08, 2011 at 03:11:45PM -0500, Jim Lesinski wrote:
I understand how to set up default values for a field using a custom
scrip. However, it seems
a bit odd to me to load a ticket with no value, and then set it only
if the person opening a
ticket doesn’t select a value. I’d like to set the value in the UI
for a new ticket, so that
it is clear to the person opening a ticket that the value has already
been set.
Does anyone know of a way to set the default values so that they are
visible when the page
actually loads for a new ticket? I understand that it may not be
possible with a scrip, but I
appreciate your suggestions.
RT-Extension-QuickCalls gives you a series of quick pre-filled ticket
Create links on your homepage. This and may give you some ideas on how
to do it.
-kevin
RT Training Sessions (http://bestpractical.com/services/training.html)
- Barcelona, Spain — November 28 & 29, 2011
It looks like RT-Extension-QuickCalls can set some values using querystring parameters, but
that doesn’t seem to be working for custom fields. Is it even possible to set values for
custom fields using querystring params? If you can, I may be able to use that.
You should be able to set Custom Fields with query string params, just
be aware that the field names it uses are interesting.
-kevin> On Tue, Nov 8, 2011 at 3:17 PM, Kevin Falcone <[1]falcone@bestpractical.com> wrote:
On Tue, Nov 08, 2011 at 03:11:45PM -0500, Jim Lesinski wrote:
> I understand how to set up default values for a field using a custom scrip. However, it
seems
> a bit odd to me to load a ticket with no value, and then set it only if the person opening
a
> ticket doesn't select a value. I'd like to set the value in the UI for a new ticket, so
that
> it is clear to the person opening a ticket that the value has already been set.
> Does anyone know of a way to set the default values so that they are visible when the page
> actually loads for a new ticket? I understand that it may not be possible with a scrip,
but I
> appreciate your suggestions.
RT-Extension-QuickCalls gives you a series of quick pre-filled ticket
Create links on your homepage. This and may give you some ideas on how
to do it.
Thanks Kevin. What do you mean by “interesting”? Can you provide an example of the format or where I can find the values I should use?
Thanks,
Jim LesinskiOn Nov 8, 2011, at 7:11 PM, Kevin Falcone falcone@bestpractical.com wrote:
On Tue, Nov 08, 2011 at 04:55:13PM -0500, Jim Lesinski wrote:
It looks like RT-Extension-QuickCalls can set some values using querystring parameters, but
that doesn’t seem to be working for custom fields. Is it even possible to set values for
custom fields using querystring params? If you can, I may be able to use that.
You should be able to set Custom Fields with query string params, just
be aware that the field names it uses are interesting.
-kevin
On Tue, Nov 8, 2011 at 3:17 PM, Kevin Falcone <[1]falcone@bestpractical.com> wrote:
On Tue, Nov 08, 2011 at 03:11:45PM -0500, Jim Lesinski wrote:
I understand how to set up default values for a field using a custom scrip. However, it
seems
a bit odd to me to load a ticket with no value, and then set it only if the person opening
a
ticket doesn’t select a value. I’d like to set the value in the UI for a new ticket, so
that
it is clear to the person opening a ticket that the value has already been set.
Does anyone know of a way to set the default values so that they are visible when the page
actually loads for a new ticket? I understand that it may not be possible with a scrip,
but I
appreciate your suggestions.
RT-Extension-QuickCalls gives you a series of quick pre-filled ticket
Create links on your homepage. This and may give you some ideas on how
to do it.
RT Training Sessions (http://bestpractical.com/services/training.html)
- Barcelona, Spain � November 28 & 29, 2011
Just to follow up - I looked at the rendered pages html source and tried
using the ID for the field as the querystring parameter I wanted to set. It
works, but as Kevin said the ID is “interesting”.
For custom fields you will be looking for something like
this: Object-RT::Ticket–CustomField-3-ValuesOn Tue, Nov 8, 2011 at 8:09 PM, Jim Lesinski jim.lesinski@gmail.com wrote:
Thanks Kevin. What do you mean by “interesting”? Can you provide an
example of the format or where I can find the values I should use?
Thanks,
Jim Lesinski
On Nov 8, 2011, at 7:11 PM, Kevin Falcone falcone@bestpractical.com wrote:
On Tue, Nov 08, 2011 at 04:55:13PM -0500, Jim Lesinski wrote:
It looks like RT-Extension-QuickCalls can set some values using
querystring parameters, but
that doesn’t seem to be working for custom fields. Is it even
possible to set values for
custom fields using querystring params? If you can, I may be able to
use that.
You should be able to set Custom Fields with query string params, just
be aware that the field names it uses are interesting.
-kevin
On Tue, Nov 8, 2011 at 3:17 PM, Kevin Falcone <[1] falcone@bestpractical.com> wrote:
On Tue, Nov 08, 2011 at 03:11:45PM -0500, Jim Lesinski wrote:
I understand how to set up default values for a field using a custom
scrip. However, it
seems
a bit odd to me to load a ticket with no value, and then set it only
if the person opening
a
ticket doesn’t select a value. I’d like to set the value in the UI for
a new ticket, so
that
it is clear to the person opening a ticket that the value has already
been set.
Does anyone know of a way to set the default values so that they are
visible when the page
actually loads for a new ticket? I understand that it may not be
possible with a scrip,
but I
appreciate your suggestions.
RT-Extension-QuickCalls gives you a series of quick pre-filled
ticket
Create links on your homepage. This and may give you some ideas on
how
to do it.
RT Training Sessions (http://bestpractical.com/services/training.html)
- Barcelona, Spain � November 28 & 29, 2011