Software Simplified Workflow v. Custom

[Athas Mark]

Jira training suggests that limiting workflows is a good thing.  I've create a standard workflow of backlog->todo->in-progress->Completed->Accepted.  With No state transition limits.

It appears a project specific (software simplified workflow) will ammend the workflow--to add a new state--if a project admin adds new columns, like "Testing."  But a custom one will not.  

Can I get that same behavior on a custom, re-used workflow?  Or do I have to 'guess' at what are all the possible combinational states project admin's would want over time?

[Kristján Geir Mathiesen · Accepted solution]

Hi @Athas Mark 

This functionality, of Project Admins being able to add a status to a workflow via boards, is limited to the Simplified Workflow only. See here.

HTH,
KGM

[Athas Mark]

So its not so discouraged to allow Jira to create a workflow and workflow schema for each and every project...  Thinking the opposite then, when an  Admin team is taking the direction to limit workflow schema count, the admins should create one workflow and workflow schema for each form of the board the organization wants to maintain.

[Kristján Geir Mathiesen]

Well, if you want the Project Admins to be able to create statuses, then you will yes be using the Simplified Workflow.

But for other purposes, you would want to keep the number of workflows down (less overhead in upkeep later down the line). General rule of thumb: keep the number of workflows at a minimum.