We have a project that uses the JIRA default workflow. We want to add ~4 statuses to replace the single Open status. They will represent early lifecycle stages for issues and show up on a new kanban board. An existing scrum board will handle the end of the cycle, the old open/resolved/closed/reponed part.
We want the kanban/PM portion to be very GH friendly where you can swap issues around to other columns at will. But we want to keep the structure and screens we already have for the scrum board. So it seems like the choice is:
A) Switch to simplified, and then add back some of the structure. Maybe by copying the simplified workflow and modifying it.
Just add the new statuses and rules ourselves, to a copy of the JIRA default workflow, don't use simplified at all.
It seems like the two questions here are:
1) Which is easier to initially setup? (minor factor really)
2) Is there some ongoing benefit or drawback to one or the other, after setup?
I feel like this page spells out some of the facts without explaining things fully:
https://confluence.atlassian.com/display/GH/Using+GreenHopper+Simplified+Workflow
It seems to entice you into using the simplified worklow, without really spell out why or what the downsides might be. So my question is, should I use the simplified workflow in my case? Or what in general would lead one to use the simplified workflow or to avoid it?
