Share and navigate
Getting a board in front of other people, and moving between boards without going back to a list.
A named board is not only somewhere to work. It is something you point other people at. Every board has a link that opens it directly, the board name in the header doubles as a menu of the other boards in your list, a dashboard tile can carry its column counts, and a project's whole set of board definitions travels as a single JSON file.
The switcher, the export and the dashboard tile need a named board, created in
AnyKanban under Boards. A link does not: a saved query opened in the hub
with ?query= has a Copy link of its own. Three of the four live in the
hub itself; the dashboard tile is a separate widget that reads the same board
definitions. The ad-hoc Board tab on a
query's results has no board definition behind it, so it has no Copy link,
no switcher and nothing to export.
Pages
- Give a board a link you can put in a wiki page:
Copy link in the board header, and the
?board=deep link that opens the board itself rather than the board list. - Move between boards without going back to the list: the board name in the header is a menu of the named boards in your list.
- Put a board summary on a dashboard: the AnyKanban board widget, with total count, per-column counts, and one click into the board it summarizes.
- Copy a set of boards into another project: Export and Import of board definitions as JSON, and the two things that do not survive the trip: the saved query a board runs, and the team it is filed under.
- Choose the board AnyKanban opens: mark one board as your default, from the list or from the board itself, so arriving takes no clicks at all.
- Who sees which boards: filing a board under a team or the project, folders, moving a board without breaking its link, and the line between what arranges your list and what Azure DevOps actually enforces.
What travels with a board, and what does not
Board definitions are shared: name, backing query, work item type, card fields, style rules, tag colors, WIP limits, definition-of-done texts, split and swimlane settings. Everyone who is shown a board sees the same configuration of it, and which team or project it is filed under decides whose list it appears in, and Azure DevOps decides which of its cards each person can see.
Your collapsed columns and lanes, your Board-or-List choice, the board you marked as your default and the board you last had open are stored per user. They are not part of the link you share, not part of the widget, and not part of an export. The person who opens your link sees the board configured as it is, arranged as they left it.