RE: [otrs] Custom CustomerUser Data affecting New Ticket Form

Here's what I did - I added fields to the existing customer_user database but did not remove first_name, last_name, etc. as they aren't valid customer information for our company. Therefore I've added hotel, city, etc. What's happening is when I search for a customer on the Phone-Ticket it "auto

Re: [otrs] Custom CustomerUser Data affecting New Ticket Form

Hi, it's difficult helping you without testing your scenario... Rebekah Hayes schrieb: > I’ve altered the customer_user table to reflect our customer base. I > added hotel, city, state, etc. I also changed the map in Config.pm to > use these fields to search and reference customers. > > >

Re: [otrs] Postmaster filter question

Hi Jason, Jason B. Loven schrieb: > I have some questions regarding how the postmaster filtering works… > > > >1. Does the filter stop at the first matched rule? Or does it > continue on to subsequent rules? It appears to process all rules > regardless of whether it has already

[otrs] Generic Agents

Hopfully somone has done this before and can help me w/ this, i'm looking for a way to make all ticket that remain open for more than one day be automatically subscribed to for a agent to watch in watch tickets. Anyone done that b4. ___ OTRS mailing list

Re: [otrs] LDAP and deleting a user

On 2/27/07 05:43, "Shue, Daniel G." <[EMAIL PROTECTED]> wrote: > When using the built in DB for customers, I've read in the Manual that > you don't delete users you that you simply make them invalid. How does > this work for LDAP? > > > Thanks, > > Daniel I believe you disable them on the LD

[otrs] LDAP and deleting a user

When using the built in DB for customers, I've read in the Manual that you don't delete users you that you simply make them invalid. How does this work for LDAP? Thanks, Daniel ___ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://li

[otrs] Postmaster filter question

I have some questions regarding how the postmaster filtering works... 1. Does the filter stop at the first matched rule? Or does it continue on to subsequent rules? It appears to process all rules regardless of whether it has already hit a match. My scenario involves finding emails from a

[otrs] Custom CustomerUser Data affecting New Ticket Form

I've altered the customer_user table to reflect our customer base. I added hotel, city, state, etc. I also changed the map in Config.pm to use these fields to search and reference customers. # customer uniq id CustomerKey => 'login', # customer # CustomerID

[otrs] Attachment in agent notificaion email

Hi list, My support team treats 90% of tickets by email. I would like to have OTRS notifiyng them when a new ticket is created but I absolutly need to forward/transfer any original attached file sent by our customer. Does anyone have experienced this and how could I set this up in OTRS ? thanks