We use one board per product line with multiple teams using the same board. Currently everyone is on Scrum with the simplified workflow. One team is moving to Kanban so we will be creating that board for them. We will need a more complicated workflow for the Kanban team, but I don't want it to screw up the other teams using Scrum. Is there a way to do this without creating a new issue type for the Kanban team?
There are two basic approaches
There is a factor that you need to think about though. Both approaches require you to stop using simplified workflows for the board.
I'm with you on that. Simplified workflows are great for teams who do "agile" well, and don't need a structured workflow. But as soon as you need a controlled process or two different ones in the same team... nope, back to proper workflows.
You can use one workflow, and use conditions on group membership to determine which transitions are available to which people. It would be complicated, but workable, as long as there is no intersection in group membership. Or you could just give each issue a custom field to designate if it was Scrum or Kanban, and make the condition based on the value of that field, or some other determinator like Component, etc.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events