Greg,
On Wed, Feb 20, 2008 at 8:34 PM, Greg Evans <[EMAIL PROTECTED]> wrote:
> All of my users are in our radius file, which is great and I am pretty sure
> that I can figure out how to import them from that using standard mySQL
> syntax and a exported .csv or similar file.
>
> The problem tha
Greg
> -Original Message-
> From: Mike Peachey [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 07, 2008 7:09 AM
> To: Greg Evans; RT Users
> Subject: Re: [rt-users] Ideas on best way to do this?
>
> Greg Evans wrote:
> > Hey Mike,
> >
>
Greg Evans wrote:
> Hey Mike,
>
> Thanks for the reply. I am attaching a screenshot of what I created for my
> tickets previously with custom fields and all of that.
>
> Maybe with my SS you can tell me if I am at least on the right track there?
Well, with regards the last four custom fields,
Ruslan,
On Feb 7, 2008 1:31 AM, Ruslan Zakirov <[EMAIL PROTECTED]> wrote:
> What we have:
> * User has Organization field
> * RT has support for searches like "Requestor.Organization = 'X'"
>
> What you have to do:
> * maintain users' field
> * replace "More about X" box with "More about X's compa
What we have:
* User has Organization field
* RT has support for searches like "Requestor.Organization = 'X'"
What you have to do:
* maintain users' field
* replace "More about X" box with "More about X's company Y"
The latter is very easy:
> find . | xargs grep 'More about'
./html/Ticket/Element
Let's not delude ourselves. Most of RT is very flexibly designed, but it's
not perfect. Maybe RT4 will be perfect but I doubt it.
I agree with your other points though. Leave the requestor field alone and
turn off email to the requestor if that is what is desired.
-Todd
__
Greg Evans wrote:
> Hey Mike,
>
> We don't really use the requestors field because the tickets don't get viewed
> or looked at by anyone but myself and my boss. We don't want the replies to
> go out to the customer, so we don't put their name in it or anything so
> everything is set up so that
Greg,
For each ticket that is created, there are links that you can create
that will show the relationship between the two (or more) tickets. Child
tickets are designed as a dependency, but a one that belongs to the same
queue as the base request. This is in case there is an administra
achey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 9:12 AM
To: Greg Evans
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] Ideas on best way to do this?
Greg Evans wrote:
> Here is what I would like to do, but I am not sure if the approach I am
> taking is one that
Leonid Mamchenkov wrote:
> Hello,
>
> On Feb 5, 2008 7:11 PM, Mike Peachey <[EMAIL PROTECTED]> wrote:
>> It certainly doesn't seem to make sense, why use the requestor's first
>> ticket as a reference point instead of the requestor account itself?
> [...]
>> Perhaps if you explained why you were l
Hello,
On Feb 5, 2008 7:11 PM, Mike Peachey <[EMAIL PROTECTED]> wrote:
> It certainly doesn't seem to make sense, why use the requestor's first
> ticket as a reference point instead of the requestor account itself?
[...]
> Perhaps if you explained why you were looking at doing it this way - an
> i
Greg Evans wrote:
> Here is what I would like to do, but I am not sure if the approach I am
> taking is one that makes sense or if I should be going about it a different
> way, so I thought I would ask ☺
> The idea is that when we create a ticket for a given user, each additional
> ticket will
Here is what I would like to do, but I am not sure if the approach I am taking
is one that makes sense or if I should be going about it a different way, so I
thought I would ask ☺
Idea for how I would like it to work
Caller 1 calls in on Issue A (Ticket #)
-->Ticket Created
13 matches
Mail list logo
