Auto-seed the folder tree
Rather than build the tree by hand, seed it from a structure you already have:- From Area Paths — each area path segment becomes a folder (trimmed, empty segments ignored).
A second source — seeding from the plan/suite hierarchy — was removed in v2.61.0, and the source picker went with it: a single remaining option had nothing left to choose, so the dialog now opens straight on the counted preview. On a real, plan-heavy project it produced a tree several times more crowded than the same project’s Area Paths, from far more requests — not through an implementation defect, but because a tree with one parent per folder cannot structurally mirror plans that share their test cases. Anything you already seeded from it is untouched.
Seeding never overwrites your work. It only ever adds folders and files unfiled cases — your manual organization is safe.
Bulk operations
Tick cases by row to build a selection that survives scrolling and resets when you change folder or filter. “Select all” is bounded to the visible, filtered results — never the entire universe — so you always know exactly what you are acting on. Assign or remove a whole batch in a single atomic write, with an exact report afterwards (assigned / moved / unchanged).Readability: counts, flat view, name warnings
- Descendant-inclusive counts — each folder shows how many cases it holds including its sub-folders, the way Xray does, so a parent folder is never misleadingly shown as empty.
- Flat view — switch from the tree to a flat list of every filed case with its full folder path. Search applies, and your choice of view is remembered.
- Sibling name warning — a non-blocking notice appears when two sibling folders share the same name (trimmed, case-insensitive), including duplicates a seed might have produced. Creating or renaming stays allowed — it is a heads-up, not a wall.
”Not in any plan” (formerly “ADO orphans”)
The node that lists cases planned nowhere is labelled “Not in any plan” (French: Non planifiés). The earlier “ADO orphans” wording was too easy to confuse with “unfiled” — two different ideas. Unfiled means you haven’t put it in a Repository folder yet; Not in any plan means Azure DevOps has it in no test plan. The definition didn’t change, only the wording.Manual ordering
Within a folder, reorder cases by drag & drop or with the keyboard (move up / move down). Each folder has a sort mode:id (default), title, or manual. The first time you reorder, the folder switches to manual sort — and switching back to an automatic sort asks for explicit confirmation, so a manual order is never overwritten silently.
Related
Repository overview
The concept, Unfiled, search and “used in”.
Generate a plan from a folder
Turn your organized folder into a real ADO plan.