Bu you still can't creat a block without an incident though right? In my environment we may create blocks based on intelligence or data and not necessarily as a reactive measure so I'm looking at how to represent that in RT.
From the desk of Nicole A. Powell.... > On Jan 4, 2016, at 2:01 PM, Jim Brandt <[email protected]> wrote: > > As a workaround, you could create a custom field to store links to one or > more other tickets. When you create the custom field, you can put a path in > the "Link values to" box and that will turn the displayed custom field into a > clickable link. (You can see this in the IP custom field in RTIR as well). > Something like this would work for an RT ticket: > > __WebPath__/Ticket/Display.html?id=__CustomField__ > > RT then replaces __WebPath__ with the path to the current RT/RTIR and it will > put the custom field value, in this case a ticket id, in the place of > __CustomField__. You can set the custom field to accept one or multiple > ticket ids. > >> On 12/30/15 10:23 AM, Nicole Powell wrote: >> Until we're able to customize the RTIR workflow I am looking for a >> workaround on how to associate blocks to tickets other than incidents. Any >> ideas or suggestions? >> >> From the desk of Nicole A. Powell.... >
