[rt-users] RT::Extension::NonWatcherRecipients

[Bunker, Robert]

One of the main problems I have with my Request Tracker installation is that 
people added on external email after a ticket is created are not subsequently 
added as CCs to a ticket.

http://blog.bestpractical.com/2013/03/keeping-track-of-extra-email-ccs.html

This extension identifies that problem but just sends out notification.  Is 
there any other extension or setting or even third-party published 
customizations which will automatically add people as CC roles on an existing 
case?

-Rob

[rt-users] Additional CCs send to ticketing system do not get added to case

[Bunker, Robert]

I have ParseNewMessageForTicketCcs enabled and new cases created by email do 
add CC'd addresses as CC roles on the ticket.

The problem I am having is that any subsequent email communication from people 
that include new addresses do not get added to roles on the ticket (and thus 
don't get updates going forward).

An example would be a user who is communicating on a case CCing their co-worker 
on an update.  I would prefer to have this person added to the case and remain 
on the case.

I would also prefer to have any new people addressed as a "To" added to case on 
subsequent emails.

Does anyone have any suggestions?


-- 
RT training in Amsterdam, March 20-21: 
http://bestpractical.com/services/training.html

Help improve RT by taking our user survey: 
https://www.surveymonkey.com/s/N23JW9T

[rt-users] Request Tracker URL http vs https

[Bunker, Robert]

RT_SiteConfig.pm contains:

Set( $WebDomain, 'domain.com' );
Set($WebPath, "/requesttracker");
Set($WebPort, 8010);
Set($rtname , "domain.com");
Set($Organization , "domain.com");
Set($WebBaseURL,"https://domain.com:8010";);

So I use BIG-IP to do SSL so apache is all standard unencrypted http
traffic.

My external access is https://domain.com:8010/requesttracker/

This forwards to the local RT install
http://local.com:8010/requesttracker/ (transparently to the end-user of
course)

This works but when performing certain functions such as just logging
in, the app then directs to http://domain.com:8010/requesttracker/ which
doesn't work.  If I flag the url in the browser address bar with https
it's fine and I load the dashboard fine.

When I logout or try to log in with wrong credentials it doesn't break
and sticks with the https/8010 scheme.

What I want to do is make sure RT is always directing to https/8010 but
I must not have it configured correctly.

Any assistance would be appreciated.

-Rob