Not to appear to be too much "Mr.Obvious" - but a well-structured wiki is cheap and easy to set up - but hard to keep structured. You might also look at systems like Trello - which aren't as flexible and impose more structure. I'm sure there are also better tools. But that's my 2 cents worth (or maybe a little less)...
On 05/06/2013 12:59 PM, Craig Constantine wrote: > Anyone care to recommend a knowledge base/tracking/journaling solution? > > Something for system journals, run logs, change tracking, procedures... that > sort of internal stuff. I'm currently running a home-grown solution but I'm > running out on the fuzzy edges trying to wrangle open issues/tickets, > scheduling recurring work, and some other bells-n-whistles. This is purely > for within-our-organization use; So I don't need, for example, a > public-facing customer request system. > > Also interested in any case studies or similar on best practices for setting > up these sorts of system. > > --Craig Constantine, http://constantine.name > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ -- Alan Robertson <[email protected]> - @OSSAlanR "Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
