[wplug-internet] Proposal to set up a ticket tracking system on the server

[Pat Barron]

I have not - but I will check it out.  Thanks!!

--Pat.

On 10/5/2016 3:31 PM, chuck at dasroot.net wrote:
> Have yinz looked at taiga?
>
> Http://taiga.io
>
> It's release planning and ticketing with integrations. We've used it 
> in the past with some success but it may not be what you're looking for
>
> On Oct 5, 2016, at 11:35 AM, Joe Prostko <joe.prostko at gmail.com 
> <mailto:joe.prostko at gmail.com>> wrote:
>
>> On Tue, Oct 4, 2016 at 11:50 AM, Pat Barron <pat at lectroid.com 
>> <mailto:pat at lectroid.com>> wrote:
>>
>> > Any comments?  Does anyone have any other lightweight ticket 
>> tracking solutions they like?  I know that things like Redmine exist, 
>> but are far too "heavyweight" for our relatively simple needs.
>>
>> I'm not the most fond of Trac, but that is mostly because the main 
>> instance of it that I use ( https://dev.haiku-os.org/ ) has 
>> additional modules enabled, and I believe some custom code.  In other 
>> words, while it usually is well-behaved, sometimes it does indeed 
>> misbehave.
>>
>> I have used Open Atrium ( http://openatrium.com ) before, but 
>> basically it is a customized Drupal distribution.  While older 
>> versions based off of Drupal 6 were highly targeted for ticketing, 
>> that seemed to take a back seat in newer versions that are basically 
>> a type of collaboration tool. Naturally, it comes with the same 
>> baggage as running Drupal as well, and requires updates to be done 
>> regularly for security and bugfixes.  I think it is overkill for our 
>> case.
>>
>> I have used osTicket ( http://osticket.com/ ) as well, and while it 
>> seems initially like it would be a good solution, it is primarily 
>> meant for customers to file tickets to an organization/company.  It 
>> probably isn't a great fit in our case for tracking our own 
>> tickets..well, or at least I think that is the use case you are 
>> targeting.  It is possible that it allows for a private issue tracker 
>> of sorts nowadays, but that certainly wasn't the case previously when 
>> I used it.
>>
>> I know you said you didn't want anything with SCM aspects, but Fossil 
>> ( http://fossil-scm.org ) offers a ticketing system along with its 
>> SCM and other functionality.  You will see that the project itself 
>> has tickets disabled though, since they were getting spammed since 
>> they allowed anybody to file a ticket.  If you do set up users 
>> though, you can make it so that anonymous people do not have the 
>> ability to file tickets.  It also lacks LDAP integration, although if 
>> you can kind of work around that by using something like 
>> mod_authnz_ldap and taking advantage of the REMOTE_USER header which 
>> Fossil understands. Fossil is a single binary, so it's not mysterious 
>> to get up and running.  That said, even though it is pretty 
>> lightweight, it may be overkill as well, since it has other 
>> functionality we probably wouldn't use.
>>
>>
>> I'm open to giving Trac a whirl, but admit I don't know squat about 
>> administering it.  I do know how to interact with it though, so maybe 
>> that counts for something.  :)
>>
>> - joe
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> wplug-internet mailing list
>> wplug-internet at wplug.org <mailto:wplug-internet at wplug.org>
>> http://www.wplug.org/mailman/listinfo/wplug-internet
>
>
> _______________________________________________
> wplug-internet mailing list
> wplug-internet at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug-internet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.wplug.org/pipermail/wplug-internet/attachments/20161005/b0270569/attachment-0001.html>