At TrackJumper, one of our goals is to create bug tracking software that allows teams to work the way they want to while providing the structure that helps keep them organized. It's not always an easy task. The more helpful and specific we get with the features we add, the more TrackJumper becomes "opinionated".
That's why our "priority" field is really a generic "status" field that you can change to suit your needs. It's why we don't encourage any preconceived notions about how you split your project up - we just give you "buckets". You can assign your buckets to users, releases, types of bugs, or anything else you come up with. We use Git, so we create a bucket for each Git branch.
It's simple, but effective. We create a git branch to try out some UI experiments, implement a new feature, or fix a complex bug. As soon as we create that branch in git, we create a corresponding bucket in TrackJumper. When the bucket is empty, we can be pretty sure it's about time to merge it back into the master branch. We then merge, delete the old branch (if appropriate) and it's bucket (if appropriate).
We'd love to hear how you prefer to organize your bugs. Email us at info@trackjumper.com or leave a comment below.
0 comments:
Post a Comment