Work Flow Good Practice - Is it good to create different Workflows for Sub status?

[prakash nagarajan]

Work Flow Status(Story/Sub Task):

We are having a Workflow for my story and we are trying to create different subs tasks like Development,QA, SIT, UAT as part of that User Story and different Work flows for each Sub task. Is this a right Approach or do we have any other way to handle the same. 

Note: Development,QA,SIT,UAT will be created as new issue type and then different workflow for each and then attaching this under US.

[Antoine Berry]

It seems a bit overkill to me to have that many different workflows for sub-tasks of one issue type. I would consider standardizing the workflow and using only one issue type. Then distinguish the sub-tasks with a list custom field ("Environment" for example). But then again, what Zachary said.

[prakash nagarajan]

It can be accomplished with Multi select Custom Field instead of creating different workflows for different sub task. Just worried as few were saying its not good Practice.

The Ask is - For Design status in Work Flow they wanted to track whether Design in Progress,Design Sign off in Progress,Design on Hold, Design Signed off. 

Approach 1 : Create Custom Field with Multi Select Option

Approach 2: Create a new Sub task Issue type as Design and create workflow like mentioned above.

Note: We have 5+ Status like Dev,Design,QA,SIT,UAT. This needs to be done for all

[Antoine Berry]

Well I do not know your specific workflow (is it for software development?) so in the end you have to figure it out. Few points which are (imo) worthy to consider :

• Do you really need sub-tasks ? It is not striking to me to have a workflow with these statuses (Dev -> Design -> QA -> SIT -> UAT). In this case you do not need a custom field.
• Consider subtask if multiple actions need to be performed within the same period, or/and different people are needed to complete each stage. In this case you can use a list custom field.
• Depending on what add-ons you are using, you can customize your Story workflow to progress or be blocked according to sub-tasks.

[Zachary Hayes]

Ideally the best practice is to create as few workflows as possible, to minimize the amount of effort is necessary to make future changes and reduce clutter and complexity. Try to accomplish as much as you can with as few workflows as possible using other schemes like the issue type screen scheme, but if you can't accomplish what is required without creating a new workflow then that's okay.

[prakash nagarajan]

It can be accomplished with Multi select Custom Field instead of creating different workflows for different sub task. Just worried as few were saying its not good Practice.

The Ask is - For Design status in Work Flow they wanted to track whether Design in Progress,Design Sign off in Progress,Design on Hold, Design Signed off. 

Approach 1 : Create Custom Field with Multi Select Option

Approach 2: Create a new Sub task Issue type as Design and create workflow like mentioned above.

Note: We have 5+ Status like Dev,Design,QA,SIT,UAT. This needs to be done for all.