JIRA Workflow vs Kanban/Scrum Board Status and workflow/Greenhopper

Juan Du Toit

Hi

I have a project that has a very simple worflow. Each issue type follows the same workflow, but screens and validations differ for each issue type. It works fine and is pretty awesome.

What happens to the workflow of each issue type in a project if I create a Kanban or Scrum board for those issues, but with more statuses?

The same question goes for a board that pulls in issues from multiple projects that has different workflows?

I want to understand the logic and how JIRA handles this. Also where would the user have to change the status? On the issue itself or on the board? What happens to the validations and screens if the board has more statuses than the workflow?

Hope this does not sound to complicated

Regrads,

Juan

Nic Brough -Adaptavist-

Think of the boards as a different way to visualise the Jira data. They don't change the workflows or do anything with the issues that you can't do in standard Jira

So you can add status to the workflow, and/or columns on the boards, and all you need to do is make sure the board mappings between status and column are updated.

Many places I know happily work with a team scrum board, several personal Kanband boards, and a handful of users who never look at boards and just work in plain Jira. It's all the same data behind the scenes, and it doesn't matter who is using what method. If you have conditions, validators, post functions and screens in a workflow, then these apply to the users on boards just as much as they do for non-board users

There are a couple of exceptions to the above. Sprint data is handled mostly by scrum boards, you don't really see/edit it anywhere else. Also, if you use "simplified workflow", then Jira creates a new workflow for the project and edits it when your users change the columns on the board (it's still a Jira workflow deep down, it's just letting more people edit it)