Repository navigation
Roadmap: offer the end of every open hand-over segment of started work - #919
Merged
Merged
Conversation
An item whose tasks hand over between repositories is drawn as segments. Once its work has begun every segment is locked, and only the segment reaching the item's end offered its end grip, so an earlier open segment showed no resize cursor and a drag on it did nothing. Every segment still open now offers its end; a segment drawn where its work ran stays fixed. Dragging an earlier segment's end pins the item's end as many days later (RoadmapPlanView.PinnedEndFor); the open segments then share the window out by effort again, so the dropped edge is not where the segment lands. The last segment pins the dropped date, as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
On the roadmap, an item whose tasks hand over between repositories is drawn as segments. Once work on it has begun, every segment is locked and only the segment that reaches the item's end offered an end grip. An earlier, still-open segment showed no resize cursor, no preview, and a drag on it did nothing on release.
Now every open segment of work in flight offers its end. Dragging an earlier segment's end pins the item's end the same number of days later — the decision taken over a per-segment pinned end, which would need new stored data.
Changes
RoadmapPlanView: a part records whether it was drawn where its work ran;EndResizableis now "in flight and not history" instead of "reaches the item's end". Finished segments stay fixed.RoadmapPlanView.PinnedEndFor(bars, bar, change): the item's drawn end (latest end of its bars) moved by how far the dragged bar's end moved. For the last segment that is the dropped date, so existing behaviour is unchanged.RoadmapBand.ApplypinsPinnedEndFor(...)instead ofchange.End.Reviewer note: for an earlier segment the dropped edge is not where it lands — after the pin, the open segments re-share the longer window by effort. Accepted trade-off.
Testing
RoadmapPlanViewHandOverTests: +2 — open segments resizable while a history segment is not; delta pin for an earlier vs the last segment.dotnet build Backlog.sln: 0 warnings, 0 errors.dotnet test Backlog.sln: 10454 total, 0 failed.…@budgetbeheer#1rendered locked, no end grip). Not re-run against a live build: the case needs in-flight hand-over data from the user's own workspace. The grip/cursor/JS path is unchanged and already works for the final segment.Related
No issue — reported in session.
Checklist
🤖 Generated with Claude Code