* Wiki pages organized by "machines", "services" and "procedures" with proper links among them (a procedure affects some services that are offered by some machines a machine hosts some services -or parts of them each service has some associated procedures and expands through one/some machines).
So, my recomendation is Edgewall's Trac because of it leaness and functionality, more or less like this: In example, a component/milestone combo provides for a nice solution for your short, unbudgeted, as time allows, personal/internal "microprojects", and being wiki-based, hierarchycal tickets can be easily mimicked using a "superticket" ticket type that links to all the related "subtickets" which in turn "backlink" to the parent. * It lacks "proper" multiproject and nested tickets support but, as I already said, that's not a problem since you are alone and workflow/procedures are basically in your head (and described on a wiki page too). You will fastly and easily group your tickets by milestones (like, say, "work as usual year 2009" or "summer campaign"), by components (like "central servers", "help desk".), by type (like "bug", "enhancement".), by priority and severity but you will be *not* forced to use them if you don't want to (as an example, shorter shops tend to use either priority or severity, but not both).
#Thinking rock custom reports code
* It allows (but not commands) tight but lean integration between wiki pages, tickets, milestones and source code management. there are not -at least by default, fixed workflows nor fancy flowcharts to the content of a project manager but absolutly unuseful for a single or a short development/multitasking group). * For a start it really helps the guy that do the thing instead of getting in his way in favor of the one that plans the thing (so, i.e. Let's have a look about how Trac fits the bill: I'd find in this case its conceptual father to be a better fit. That's where even such a fine tool like Redmine is a bit of an overkill. At any given time, I need to be able to jump back to one of these items and pick up where I left off"ġ) His best tool must be his mind: he must use it to set his own procedures (and exceptions), so pointing to reads like David Allen's "Getting Things Done" or "Limoncelli's Time Management for System Administrators" are a foremost.Ģ) Given the right ideas are in his mind and given that it's a solo show, the leaner the tools the better: he don't need contrains on the tools when he can adopt them by his own criteria. "I work as the sole IT employee I've always got multiple programming (both new systems and improvements/changes to existing systems), integration, research, maintenance tasks/projects on my To Do list, in varying stages of completion. I know I'm not alone in this problem, so what do you guys (gals) use to address this?" In some of these projects I may want to include proprietary information, which I really don't want floating out in the cloud outside of my control. Ideally it would be a desktop app, but a locally-hostable web app would be okay. Essentially what I'd want would be a Task List on steroids, allowing for hierarchical subtasks, attachments, and prioritization. I looked at using MS Project / OpenProj, but they want an individual file for each project, and I want at least the project/task list all on one screen. If it's been a while, I'll end up losing an hour or two just tracking everything down. I am currently using Outlook Tasks, and then end up referencing my notebook and email for those dates to figure out exactly where I left off. At any given time, I need to be able to jump back to one of these items and pick up where I left off. As a result, I've always got multiple programming (both new systems and improvements/changes to existing systems), integration, research, maintenance tasks/projects on my To Do list, in varying stages of completion. As seems to be true with many small companies, the priorities seem to shift quite frequently. I handle programming, support, pretty much anything that is IT related, or even that plugs in. JerBear0 writes "I work as the sole IT employee at a company of about 50 people.