EclipseStore To .board/ Migration Shift

When Microsoft quietly moved legacy issue tracking from EclipseStore to .board/ last week, it sparked a subtle but significant shift in how teams manage open work. One-off migration commands now slice through months of ticket data - organizing backlogs, reclassifying statuses, and rewriting history into clean, board-friendly ISSUE.md files. This isn’t just file formatting; it’s a cultural reset in how workspace teams visualize progress.

Here’s the core: each issue maps directly to a board column - Backlog, Todo, InProgress, Review, Done, Archive - based on IssueState. Backlogs go to backlog/, active tasks stay Todo, and InProgress shifts to in-progress/; completed work archives cleanly, while duplicated or failed issues go to archive.

Behind the scenes, this system leans into US workplace psychology: clear state labels reduce ambiguity, while consistent structure fuels transparency. Think of it as digital ritual - each migrated ticket gets its place, just like in a physical desk.

But here’s the catch: many teams assume all states are covered, yet some rarely used categories - like ‘HumanReview/Rework’ - rarely get migrated, creating invisible gaps. Plus, skipping already-migrated issues requires strict tracking - otherwise duplicates creep in.

Mixed in is a growing debate: does migrating old issues risk oversimplifying context? Users report confusion when nuanced state histories get flattened into board columns.

The bottom line: migration works best when paired with clear governance. Migrate, verify, and guard against silent omissions - because the line between order and chaos is thinner than the new .board/ folder.

Does your team treat migration as a one-time fix, or a living process?