A sub-status doesn't really do much for you, it's just a field.
You could base a swimlane on the custom field instead, but you'd lose the in-progress swimlane. Or you could meld them and have two swimlanes (jql would be status = x and field = y, and status = x and field != y)
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs