Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Control other projects' user stories from a different kanban board.


We have a design team that is working with 6 other teams as a shared service.

The design team, needs to be able to see and control the state of the stories in the other 6 backlogs. We've done that much (tag stories as "design", so that they appear in Design team's board).

What we've found is that these stories inherit their parent boards' workflow states, so in the design team's kanban board, when we move a story, depending on its workflow steps, the appropriate steps are shown on the board under "In Progress".

Are there any best practices for working in this fashion?

The aim here is for the design team to control stories found in other backlogs, to avoid creating their own stories.

1 answer

0 votes

The best practice is quite simple - make sure your people understand what they are looking at and how it works.

A board is a view of a set of issues, not a container.  Anything you do to an issue in one board updates the issue, including workflow actions (workflows are executed by issues in projects, not the boards), and hence all the other views (boards) will show that change, although they may need refreshing to pick it up.

You will benefit from documenting everyone's process, so that a person can see what other teams do and where they fit in.

It is well worth getting all the stakeholders together to discuss the use of status - you want them to agree on a clear list across all the teams who may be sharing, as you don't want things like status of "to do" and "to-do" in a flow.  Rename them to be clear - "waiting for dev assessment" and "waiting for test" (clunky, but clear)

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events