[Noisebridge-discuss] Ultra-lightweight issue tracker/CRM?

[Will Sargent]

Have you tried hiveminder.com?  It seems like the sort of thing you want.

Will.

On Fri, Jan 29, 2010 at 4:26 PM, Sai Emrys <noisebridge at saizai.com> wrote:

> For conlang.org, we get a bunch of email for which it's unclear whose
> job it is to handle it. This is, I think, true also of
> press at noisebridge.net and other group contact points.
>
> As a result, sometimes mails can go unresponded-to, or issues
> unresolved / forgotten, because everyone thought someone else would do
> it, or just because someone did one step and forgot to follow up.
>
> This is conceptually extremely similar to standard issue tracking -
> though in this case the issues aren't really about some app, they're
> anything that might come in by email.
>
> It seems to me that some sort of lightweight issue tracker / CRM /
> shared todo list thingy would be very useful here - one would be able
> to more easily see what things were closed, etc. Ideally, it'd be
> mostly transparent; it would monitor the group email address,
> automatically assign tickets, take most of its commands by scraping
> normal email traffic.
>
> However, all the trackers I know of are way too heavy for this
> purpose, or specialized for something else (e.g. customer support in a
> largish corporation; bugs relating to some set of apps; etc). I don't
> want to turn off our contacts by having them deal with a full-on
> ticketing system - it should be transparent to them - and I don't want
> the hassle of something that has a lot of overhead.
>
> Do any of you know an app that'd be suited to this use?
>
> Thanks,
> - Sai
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20100129/46c63991/attachment-0003.html>