[Cialug] FOSS Incident tracking

[Josh More]

I know that this is obvious to many, but I have to weigh in here... If
you're tracking incidents, the critical element isn't architecture or
feature set.  It's whether your people will actually use the system.
So, instead of going off the recommendations of this list (which are
good), spin up a few VMs and ask your team which one feels right.
You're far more likely to build a successful security management team
that way.

-Josh

On Thu, Nov 17, 2011 at 9:49 AM, Matthew Nuzum <newz at bearfruit.org> wrote:
> On Thu, Nov 17, 2011 at 8:41 AM, L. V. Lammert <lvl at omnitec.net> wrote:
>>
>> On Thu, 17 Nov 2011, chris rheinherren wrote:
>>
>> > I have a friend who is looking for, in his words:
>> >
>> > "Looking for a good open source incident tracking system, any ideas"
>> >
>> > so if you have any suggestions, fire away.
>> >
>> While not explicitly an 'incident tracking system', we have been using
>> Redmine for years to track issues here; one of the best features is that
>> it allows many diverse 'information models' by client/customer.
>>
>
> +1 on redmine. I've also used Trac which is very similar. At one time I had
> Trac configured so that you could create new tickets by sending an e-mail.
> If you want an e-mail interface, RT is hard to beat (but also a bit harder
> to setup and manage).
> The main difference between redmine and trac is that redmine is ruby on
> rails, trac is python.
>
> --
> Matthew Nuzum
> newz2000 on freenode, skype, linkedin and twitter
>
> ♫ You're never fully dressed without a smile! ♫
>
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>
>