I’m a bit at a loss on where to start searching for a solution to this: How
to place a custom form(*) on Display.html. Ideally, that would be placed on
top of the “History” section, but there is some flexibility on placement if
it gets easier to implement.
(*) A single button who whould perform a POST action to a non-RT-URL,
having the ticket Id as parameter.
– Matthias
I’m a bit at a loss on where to start searching for a solution to this: How to place a custom
form() on Display.html. Ideally, that would be placed on top of the “History” section, but
there is some flexibility on placement if it gets easier to implement.
() A single button who whould perform a POST action to a non-RT-URL, having the ticket Id as
parameter.
You probably want to read about Callbacks - you can use them to insert
HTML into various pages in RT (or to change things about the page, but
in your case you just want to insert some HTML).
http://requesttracker.wikia.com/wiki/Customizing
-kevin
Matthias,
Not sure of your use case but we have situation where we do a HTTP POST
from a scrip to a non RT URL based on certain ticket conditions. RT makes
this very easy to automate and not have to involve the human.
Not sure if that works for you.
RobertOn Wed, Apr 17, 2013 at 10:52 AM, Kevin Falcone falcone@bestpractical.comwrote:
On Wed, Apr 17, 2013 at 04:40:30PM +0200, Matthias Leisi wrote:
I’m a bit at a loss on where to start searching for a solution to
this: How to place a custom
form() on Display.html. Ideally, that would be placed on top of the
“History” section, but
there is some flexibility on placement if it gets easier to implement.
() A single button who whould perform a POST action to a non-RT-URL,
having the ticket Id as
parameter.You probably want to read about Callbacks - you can use them to insert
HTML into various pages in RT (or to change things about the page, but
in your case you just want to insert some HTML).http://requesttracker.wikia.com/wiki/Customizing
-kevin