Version 3 workflow – a little preview
One of the last things (yes, we have more to show) to enter version 3 before the beta release is workflow support. If you’ve used trackers with workflow support before, you’ll know what I’m talking about – but if you haven’t, I’ll give you a very short introduction here. Oh, and there’s a screenshot, too.
The Bug Genie has never really supported any structured workflow. One of our weaknesses have been the “see-all, set-all” fields mentality that has stayed with us in both version 1 and version 2. Workflow support has been high up on the list of feature requests, and now it’s finally sneaking itself in.
Workflow support basically means that you can define the lifecycle of an issue. When can you move an issue from one status to another? Who can move it, and when can they do it? Not to mention, when can they *not*? Bigger teams with testers, developers and project managers often ask for this feature, as they try and keep their team responsibilities separated – and that’s a good thing!
We’ve looked at how other trackers implement workflow support, and both FogBugz (with its sub-par “workflow support”), JIRA, Mantis and Trac have been researched to see how we best can implement this feature. We decided to implement it along the same lines as JIRA does, and if you’ve ever worked with JIRA’s workflow capabilities you’ll hopefully find yourself right at home.
We are trying to get as many workflow features in as possible, although not all possible features will be enabled in the default workflow. You will be able to specify your own workflow, though, so don’t worry 😉 If you have tips and recommendations in this regard, let us know! We have comment sections, forums and email adresses, and you know where to find them.
Oh, yeah, there was suppose to be a screenshot. Well, this is where we’re at: