I think you want to use something other than Team Board and it's "stealth" column names under field "Flow State" for more htan one team. As the name implies,
Team Board is for teams. I've actually used "Flow State" in some custom list and board apps showing how the Team Board customization can be extended a bit.
For a train or large branch, you probably want to use
custom fields, as some people in my workspace have done. Then the same field values can be used for columns in Kanban Boards across teams, as well as reporting dashboards.
As the reach of this shared increases, anticipate some people wanting to standardize these values, restricting teams who want their own flavour of board columns. ;)
------------------------------
SM, Application Support
Cigna
------------------------------
Original Message:
Sent: 10-16-2020 01:38 PM
From: Pearce Cowart
Subject: How to apply custom flowstate values in Team Boards to parent board
For tracking purposes, a group of teams needed more granular values than ScheduleState allows. We customized their Team Boards (siblings and unique parent) accordingly, all have the same FlowStates defined.
But we also need a similar view that functions as a "master" view at the parent level, displaying all cards and their states for the parent and all children, consistent with the individual Team Boards.
Team Boards seem to be "hardwired" to their respective project... no ready linkage to siblings or parents.
Kanban Board settings do not allow choosing FlowState for driving the columns. My predecessor circumvented all this with a custom field, which is drudgery to maintain per artifact.
Am I overlooking some nuance here? Is there a straightforward alternative to accomplish this?