Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

55 views 0 6
Read article

Community Events

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

Events near you