I found this is an issue in working. 
http://issues.bestpractical.com/Ticket/Display.html?id=18001&user=guest&password=guest

Any ideas when this would be completed?

From: [email protected] 
[mailto:[email protected]] On Behalf Of Izz Abdullah
Sent: Thursday, September 22, 2011 5:00 PM
To: [email protected]
Subject: [rt-users] Can't change relative path to saved search aftermigration 
(3.8.4 -> 4.0.2)

Hello all,

I have setup a new instance of Request Tracker 4.0.2 and imported our 3.8.4 
database to test before cutting off the 3.8.4 system.  In some saved searches 
created in 3.8.4, we have "/rt" at the beginning.  I opted not to do this in 
the 4.0.2 installation and basically have a https site internally which links 
to LDAP for authentication with the url of 'helpdesk'.  Notice, there is NOT 
helpdesk/rt.

In the Advanced portion of editing the query, I see in the format the following 
example:
'   <b><a href="/rt/Ticket/Display.html?id=__id__">__id__</a></b>/TITLE:#',
'<b><a 
href="/rt/Ticket/Display.html?id=__id__">__Subject__</a></b>/TITLE:Subject',
'__Status__',
'__QueueName__',
'__OwnerName__',
'__Priority__',
'__NEWLINE__',
'',
'<small>__Requestors__</small>',
'<small>__CreatedRelative__</small>',
'<small>__ToldRelative__</small>',
'<small>__LastUpdatedRelative__</small>',
'<small>__TimeLeft__</small>'

I have removed /rt from the beginning and hit 'Apply' to apply the changes, yet 
it is NOT staying that way.  I have also tried replacing /rt with __WEBPATH__ 
and it still will not hold the changes.  It automagically reverts back to 
having the /rt in the beginning of the relative path.  Any suggestions other 
than recreating the saved searches within the new system?

Thanks in advance!
--------
RT Training Sessions (http://bestpractical.com/services/training.html)
*  Chicago, IL, USA — September 26 & 27, 2011
*  San Francisco, CA, USA — October 18 & 19, 2011
*  Washington DC, USA — October 31 & November 1, 2011
*  Melbourne VIC, Australia — November 28 & 29, 2011
*  Barcelona, Spain — November 28 & 29, 2011

Reply via email to