Wrike as online bugtracking software: Part II. Creative approach to task statuses

Traditional bug-tracking systems have many statuses with which to tailor software development needs such as “Fixed”, “Verified Fixed”, “Closed”, etc. We are not working on a bug tracking system while we still want to use our lovely and convenient collaboration software for tracking bugs.

How did we approach that? Instead of writing a sub-system that makes your life more complex by allowing you to configure your own statuses and then… fail to work in collaborative environment open to everybody our team agreed to use a “deferred” status when the bug is fixed and “completed”, when the fix is tested.

comments powered by Disqus