Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

While this heavily depends on the user group bug trackers make it easier to self-organise topics. A few open-ended issues for general chatting (or some other platform of your choosing for that, discord or whatever) but more narrowly defined issues (be it a bug, be it a suggestion for improvement) get a new ticket number and are tracked separately. 

With this the general discussion is not cluttered with solved stuff and an idea graveyard but one can still point newcomers to it - often faster than to answer the same questions for the umpteenth time.

A typical use case is balancing: The planned combat system *will* need to be revisited quite often, and instead of discussions all over the place (see page 1, 4 and 16 of the forum thread "Rewind 0.2" and yesterday's night discussion in IRC) all comments and suggestions are tracked in #0815.

My 2 cent : )

Hmmm, I'll look into this a bit. Right now, every time you say "Bug Tracker", I think of the actual "BugTracker" software, which conjures nightmares for me based on my work experiences with it before we moved to Jira. So I think I'm having an emotional reaction to that as a work tool without having any experience using it as a community-resources tool. 

My at-home experience with online communities is with Forums. Which is what my husband knows best, too. I might look to see if there is a way to incorporate an issue tracker into an online forum (that isn't too expensive.) The more locations we have to visit in order to research something, the less likely it is to get researched. That's just human nature. Similarly, if community is over here and issue reporting is over there, that set-up lowers the (already small) likelihood of people checking to see if their issue was already reported before reporting it. 

Maybe over the weekend I'll look to see if there are any integrated solutions we could leverage. And I'll check to see what he actually prefers. My life revolves heavily around the Software Development Lifecycle, but his doesn't. So he might not actually be comfortable with using an issue tracker. I'll find out.

Thanks for the idea!

You could take a look at sf.net - one has not to use the code hosting (and, arguable, sourceforge is not a good place to do this anymore), but it gives a (mostly) fine project environment, including forum, wiki and tracker functionality.