be careful here. If issues start disappearing from the Kanban board that too may cause confusion. The point is to step back and assess the purpose of having two boards and then ‘design’ the right solution.
If one team works on certain issues and they use Scrum process while others use Kanban to work the balance of the issue then establish a means of separating the two. For example, you could choose components to define and separate the two or you can create a custom field to do the same or you could even use labels, note I’m not a big fan of the latter. Then use this in your board filters to separate them into two buckets.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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