On 15-May-07, at 4:01 AM, Gianluca Sforna wrote:
> On 5/14/07, Martin Fuchs <martin-fuchs gmx.net> wrote:
>> Hello,
>>
>>> I built a similar customization for a client
recently. They had an
>>> external database copy that was the slave to a
master internal
>>> database. Bugs updated in the external database
were synchronized to
>>> the internal one.
>>
>>> I'm thinking about generalizing it if there
is interest.
>>
>> This seems to be a very common setup: an external
Mantis instance
>> with access for the cusomer and an internal Mantis
installation for
>> developer access and internal bug tracking.
>
> This setup sounds like a workaround for some missing
flexibility in
> the access/permissions handling logic.
>
The rationale for the external system is based on IT
security
issues. With internal and external issues in the same
tracker, there
is some possibility that external people might see these
issues,
--
Glenn Henshaw Logical Outcome Ltd.
e: thraxisp logicaloutcome.ca w: www.logicaloutcome.ca
Mantis Developer and User
------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
mantisbt-dev mailing list
mantisbt-dev lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-d
ev
|