Requirements of an issue/bug tracker
- by James Brooks
I've been looking at various issue/bug trackers available on the net. There are some very good ones, but I'm unable to use them as my server does not support Perl/Ruby (for example), I'm not too bothered however because I am able to write code in PHP and as such would prefer something in that language.
So I've taken it upon myself to write a custom issue tracker system. As of now it's in early planning stages, and before I continue, I'd like to find out what people need from such an application.
My current list of things to add include:
Creating/Editing/Deleting issues - both on user and admin level
Related issues (similar to that of STO)
Admins will be able to create builds/milestones and version control of projects
Admins will be able to assign users/groups to a project
Roadmap of projects
Possible SVN integration with Git? What do you think?
There are a couple more things I'd like to add, but I'm sure you'll think of a better way of adding such feature.
What would you like to see from an issue tracker?
