Scalability of Jira Simplified Workflow

[kevinstembridge]

The Jira Simplified Workflow allows each project to customise the columns they use on their Jira Board and allows a card to be dragged from any column to any other column.

Am I correct in thinking that this results in an instance of a Workflow for each project? 

Does this have any impact on scalability? My organisation has over 1000 projects in Jira. If a large number of them switch to simplified workflow will Jira grind to a halt?

[Nic Brough -Adaptavist- · Accepted solution]

It's not quite by project - a board can include many projects, and if the workflow is simplified by the board, it's a single workflow shared by all the projects.

But, yes, you will find that the list of workflows becomes rapidly very long, one for each simplified board.  It will not directly impact your performance at scale though - workflows only impose load as they are used, and having a lot of them is more of a pain for admins and consistency of usage, than it is for load on the machine.

[kevinstembridge]

Hi @Nic Brough -Adaptavist- ,

"workflows only impose load as they are used"

Just so I understand correctly... would that mean that, for example, 100 projects sharing a single workflow would see a similar load as 100 projects each with their own simplified workflow? (assuming one board per project)

[Nic Brough -Adaptavist-]

Yep.  (Assuming the same profile of usage by people)

[Hernan Halabi - Elite IT Consulting Group]

Hello @kevinstembridge simplified workflow don't escalate at all. You end having tons of workflows and tons of different status for the same stuff like done closed ready completed finished and any other synonyms you can think of. It will impact usability and reporting sooner than performance but in the end it could impact that as well