Ken Foskey <[email protected]> writes:
> On Wed, 2009-03-11 at 11:23 +1100, Daniel Pittman wrote:
>
>> The biggest thing, though, is for you to identify what you actually want
>> to achieve with this. Without knowing that there are some very
>> different options available, and probably only some will help you.
>
> Multiple clients, different applications and projects per client. The
> different clients should not even know that the others exist. Right
> now it is about bug tracking but a full management process would be
> nice in the future.
Well, from my experience you have two options in the free space:
1. Set up a separate bug tracking system (eg trac, bugzilla) for each
client and/or project.
2. Use RT, and configure it with appropriate security.
You are not going to get project planning, etc, out of RT though, since
it is just a ticket management system. Sadly, you won't get the
multi-client security out of anything else, though, so you are kind of
stuck.
Um, unless you pay big $$$ to someone commercial, which I don't
recommend; it usually doesn't pay for itself.
> I was going to set up a wiki as well so if this was integrated it
> would be nice. Ability to store email for traceability would be good.
RT handles the later, but not the wiki integration as such. It does
have stable, predictable URL support, the ability to extend the UI and a
good scripting API, though, so it is possible to integrate it to
whatever external tools you wish.
> Ability to totally remove projects from the online once closed.
RT doesn't delete things, but you can mark them "deleted" and they never
show up unless you specifically search them. This is a feature. :)
For others ... I don't know. We wouldn't use such a feature.
> There are some potentially huge files in these projects.
You would want to store those in your VCS, not the ticketing system, if
at all possible. Which VCS is best is a whole different discussion.
> Ability to restore projects, to main server or a backup server, to
> locate information on a closed project.
...as noted, we wouldn't use such a feature, since we want to refer to
historical projects if the issue comes up.[1]
Regards,
Daniel
Footnotes:
[1] I suppose that after seven or ten years of project completion, when
it isn't going to be refered to ever again we might consider it,
but why bother? Storage is stupidly inexpensive...
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
