On 27 May 2005 at 14:20, Jerome Alet wrote:
> > If I remember correctly, there's one way... let me find it... Yes,
> > it's called
> > "CustomerPanelOwnSelection". It's something like:
> >
> > # CustomerPanelOwnSelection
> > # (If this is in use, "just this selection is valid" fo
Hi,
On Fri, May 27, 2005 at 02:15:51PM +0200, Victor Rodriguez Cortes wrote:
>
> Writing as I think (and about something I don't really know ;), OTRS
> was
> developed initially for MySQL and maybe MySQL don't support (or didn't in the
> past)
> that feature.
Ah, yes you're probably ri
AFAIK, that option is just for mail tickets (read as received by mail
by OTRS), a
not for the ones created through the web interface...
On 27 May 2005 at 12:25, Jerome Alet wrote:
> On Fri, May 27, 2005 at 11:39:37AM +0200, Yann Richard wrote:
> >
> > # PostmasterDefaultQueue
> >
On 27 May 2005 at 11:47, Jerome Alet wrote:
> > With OTRS you don't need to access the database directly, except in
> > very rare
> > occasions (disaster recovery, corrupted tables, etc).
>
> I beg to differ.
>
> Having relational integrity constraints is an important part of having
> a
On Fri, May 27, 2005 at 11:39:37AM +0200, Yann Richard wrote:
>
> # PostmasterDefaultQueue
> # (The default queue of all.) [default: Raw]
> $Self->{PostmasterDefaultQueue} = 'Your Personnal Queue';
>
> This Queue MUST be created before via admin web interface.
This doesn't seem to wo
On Fri, May 27, 2005 at 11:36:20AM +0200, Victor Rodriguez Cortes wrote:
>
> With OTRS you don't need to access the database directly, except in
> very rare
> occasions (disaster recovery, corrupted tables, etc).
I beg to differ.
Having relational integrity constraints is an important pa
Jerome Alet a écrit :
>Hi,
>
>I've setup the OTRS 1.3.2p01-5 Debian package and it now works like
>a charm with PostgreSQL. OTRS is really great stuff !
>
>Now I'm wondering : I'd like to propose to customers the choice
>between only two queues with names I'll choose, but actually there
>are seve
Hi!
With OTRS you don't need to access the database directly, except in
very rare
occasions (disaster recovery, corrupted tables, etc). To disable the default
queues you
have 2 options:
- Rename them to something usefull for you.
- Disable them, so they won't be shown (mark as i
Hi,
I've setup the OTRS 1.3.2p01-5 Debian package and it now works like
a charm with PostgreSQL. OTRS is really great stuff !
Now I'm wondering : I'd like to propose to customers the choice
between only two queues with names I'll choose, but actually there
are several predefined queues : 'Raw',
