0.7.0
Added
- Clicking a row folds it is now a toolbar toggle, beside the completed-items eye. It
moves into the⋯menu on a narrow pane, and it is remembered per saved view on this
device — beside the collapse state, like the projection and the focus level — rather
than in the.basefile. So it is yours rather than everyone's: a base shared with a
colleague no longer carries your habit of clicking to fold. There is no
Handling items → Clicking an item view option any more; aclickActionkey in a
base written before this is ignored, and the toggle starts from "opens the note". - Folding on click now covers the roadmap's timeline as well as the tree: a click on a
timeline row folds the rows below it, exactly as the row's own chevron does. Cards — on
a board, in a horizon bucket, on the shelf — still open their note, since a card lists
its children on its own face rather than folding rows. The toolbar toggle is drawn on
the tree and the timeline for the same reason. - A test catalog. Two new types,
Test suiteandTest case, form a ladder of their
own — a suite holds cases, a case holds tasks — beside the plan's Epic → Feature → PBI →
Task rather than inside it. A suite is the top of that ladder, so tests are a catalog with
an order you chose rather than work filed under a requirement. The toolbar's new Tests
projection draws it, and you can walk a suite from the top with the plan out of the way. - Your plan does not change when you start writing tests. The tree, the boards and the
roadmap draw exactly what they drew before: a test is not a row, not a card, not a bar, and
not a number in anyone's progress. A test parented under a plan item by mistake still shows
up — in the catalog, as a root of its own — rather than vanishing, and the same holds the
other way for a plan item parented under a test. - Both new types are told apart at a glance the way every other type is, with the outlined
badge that marks a row as a test. - An assignee property: name it in the view options (or press ✨ and let the view bind
and backfillassignee), then set it from the row's menu or its chip. The names on
offer are the ones the base's own results already carry — plus anything typed into
New assignee... — so there is no list to declare and nothing to keep in step. - A Test management group in the view options: name a test state property (or leave
it unbound to share the plan's own state property), list the test workflow's states in order,
and say which of those count as done. A test catalog row's state chip and its
Set statenow read and write that state independently of the plan's, whichever
property the two end up sharing or not.
Changed
- Obsidian 1.12.0 or newer is now required (was 1.10.2). The Bases custom-view API
opened in 1.10.2, but a view's options callback was not handed the base's own
configuration until 1.12.0 — so on older versions this view's options menu showed the
shippeddocs/…folders as the type-folder defaults inside any other base, and offered
no WIP-limit or column-policy box at all. Nothing else was affected: the tree, the board
and the roadmap all worked. Obsidian keeps serving 0.6.0 to vaults below the new floor. - The toolbar now leads with the projection switcher and puts New beside it, and the
dividers in the head of the row are gone — between those two, and in front of the
roadmap's own controls. Each group is set off by spacing instead: a bordered button group
already says where one control ends and the next begins.
Both still sit at the head of the row, which is what keeps them on screen at the
narrowest pane. - Dependencies work in a base that has never named the property. The bar connector and
the row menu's Depends on… used to be withheld until the dependency property was
bound in the view options — which Obsidian's own picker cannot offer until some note
already carries it, so the feature was hidden in exactly the vault that had never used
it. Making the first link now bindsdependsOnfor you and says so. Clearing the option
still turns the feature off, and an option you have already set is never changed.
The handle costs what it draws: on the dated axis with 811 bars expanded, a render goes
from ~274ms to ~318ms. - Large backlogs render about two and a half times faster with every row expanded: the
tree now lets the browser skip layout for rows scrolled out of the pane. Measured at 832
expanded rows, a full render goes from ~718ms to ~283ms; at 1632 rows, from ~1089ms to
~446ms. Test casenow wears its own colour, cyan, instead of sharingTest suite's orange —
the outlined border that marks both as tests is unchanged, only which hue each fills.
Removed
- Dragging an item onto the empty space below the tree no longer makes it top-level,
and neither does the Move to top level strip that used to appear there during a drag
— the strip is gone as well. Making an item top-level is a deliberate action now:
Outdent, from the row's context menu or Alt+Left, makes a row a sibling of its own
parent, so a row one level down becomes top-level. It climbs one level at a time, so a
deeply nested item takes a few presses. Nothing about your notes changes, and nothing
needs migrating. - Assign item type when moving is gone, and a move now never rewrites a note's type.
The option re-typed a whole moved subtree to match its new position. It was off by
default, it was the only thing in the plugin that changed atypeyou had written, and
a review found one of its safety guards had nothing checking it — losing that guard let
an unrelated drag turn a hand-nestedTest suiteinto plan work and drop it out of the
test catalog. Removing the feature removes that risk entirely. Dragging, indenting,
outdenting and clearing a parent link all write the parent and the rank and nothing
else; Set type is how you change a type. If an existing base still has the setting
saved, it is simply ignored — nothing to migrate and nothing to clean up. - The fallback that filled the view options menu when Obsidian handed the view no
configuration. Requiring the floor above is what makes that menu describe the base it
is open in, always.
Fixed
- The roadmap no longer stops responding to the pointer after a drag. If the view
refreshed while a card or bar was being dragged — which a session spent drawing
dependencies does constantly, since every link is a write — the drag left its state
behind on the pane for good: rows stopped highlighting on hover, the dependency
connector never appeared again, and no further drag could be started. The drop itself
had landed correctly, which is why nothing looked wrong until the pane went dead.
Reopening the base was the only way out. - Hovering rows in a large backlog is no longer laggy. Deciding whether a title or a type
badge needed its full-text tooltip measured the element inside the hover event itself,
which forced the whole tree to be laid out again on every hover — 65.7ms per hover at
832 rows. Both now carry their full text always, so nothing measures and nothing is
hidden: the only visible difference is a tooltip on a title that already fits.
What's Changed
- Follow-up pass: split the toolbar, cut the comment essays, file the drag decision by @Luis85 in #121
- Introduce CHANGELOG.md, checked against every version bump by @Luis85 in #122
- Let a state be given a colour, and keep the slot as the default by @Luis85 in #124
- Add an assignee property, and split the configuration into four modules by @Luis85 in #126
- A folder-note layout for the demo fixture, and an honest account of harness colour by @Luis85 in #125
- Pick a state's colour, in a dialog Bases cannot host by @Luis85 in #127
- Measure what a large backlog costs, then fix the three things it found by @Luis85 in #128
- Rework the toolbar head, and put the click-action option on the row by @Luis85 in #129
- Remove the "Move to top level" strip, and fix the drag state it stranded by @Luis85 in #130
- Test management, increment 1: the test catalog by @Luis85 in #123
- 0.7.0 by @Luis85 in #120
Full Changelog: 0.6.0...0.7.0