I am trying to define a setup where I would have two workflows, in short :
- a long workflow, something like (new -> analysed -> in progress -> tested -> deployed -> closed)
- and a short one, something like (new -> in progress -> closed)
My current and default workflow is the long one.
I managed to get the short workflow by disabling some steps through the web admin interface.
But I would like to find an automated way to make this faster and less error prone.
One answer would be to have the functionality asked by dregad in 2010 : define a workflow for a parent project and inherite this workflow for any subproject. I tested it but it does not seem to have been implemented since then.
Another possibility would be have a parameter for projects and get the workflow depending on this parameter, something like proposed in this post with issues categories (and idealy without having to disable API warning at the end).
I also thought to write some scripts to manage it through the REST API but it seems workflow cannot be modified from it.
Any ideas ? Am I missing something easier ?
Thanks a lot.