You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm working with a team that has a few different product teams, each of which have their own project boards, workflows and statuses - but share the basis issue types (bug, tasks, story, epic etc).
Each of these project boards/backlogs also (using custom fields/queries) can push issues to other product teams boards. Which can cause a bit of a nightmare with mapping statuses.
Some of the teams are working in a 'sprint approach', while others are utilising Kanban. All are currently company managed projects.
Does anyone have any recommendations on best practice for setting up the team boards, to make it easier to map statuses (even if it's too different workflows) as they are consistently tweaking and evolving their workflows to align more with the way they deliver, so it's never the same from week to week necessarily.