On 25-09-2004 at 23:02, Robert Kehl wrote:
You could you set the option 'Move::ForceUnlockAfterMove' to 1 in Config.pm. That way, tickets get unlocked after being moved. Alas, all of them ge always unlocked then...
Wonderful, I set Move::ForceUnlockAfterMove. However I think there should be a checkbox named "Lock tickets" in the Bulk Action interface, since Move::ForceUnlockAfterMove is too much general for this single purpose. I have one more feature request (btw, why not using an online tracker for feature requests?). OTRS often replaces e-mail addresses with customer database addresses (see AgentCompose.pm), and I don't like this since we *must* answer to our clients using the address they sent mail from. I modified my AgentCompose.pm as following: # use database email if ($Customer{UserEmail} && $Data{ToEmail} !~ /^\Q$Customer{UserEmail}\E$/i) { $Output .= $Self->{LayoutObject}->Notify( Info => 'To: added database email!', ); $Data{To} .= ', ' . $Customer{UserEmail}; ##Adding, not replacing! } It would be better to: - add $Customer{UserEmail} to CC: instead of To: - use a config option to choose between replacing, adding or no action Any feedback from users and/or developers about this? It should be pretty easy to implement these changes. - Alessandro Ranellucci