It’s been a busy few weeks for the Developer Issue Tracking System (DITS). We’ve hit several major milestones that significantly improve both the user experience and the long-term maintainability of the project. Here’s a look at what’s been happening in the last six pull requests.

Keyboard-First Navigation

For power users, efficiency is everything. We’ve just completed a major push for keyboard command navigation. You can now navigate through issues and board views with ease, reducing reliance on the mouse and keeping you in the “flow” state. This completes a comprehensive set of keyboard commands designed to make DITS feel more like a high-performance terminal.

Polished Kanban Experience

The Kanban board is the heart of DITS, and it just got a lot smoother. We’ve finalized the drag-and-drop functionality using @dnd-kit. Transitions are more fluid, and the interaction model is more intuitive, making it easier than ever to manage your issue pipeline.

Reaching the 100% Milestone

One of our biggest technical wins recently has been in the realm of quality assurance. We’ve significantly beefed up our test suites across the board:

• Storybook: 100% coverage. Every UI component is now documented and tested in isolation.
• Backend: 80% coverage.
• Client: 70% coverage.

Investment in testing infrastructure means we can move faster with confidence, knowing that new features won’t break existing workflows.

Streamlined Organization: Areas and Labels

Work organization is often about the little details. We’ve introduced a dedicated Area management UI, allowing users to define work streams more clearly.

Furthermore, the Label Management UI has been revamped. A key highlight is the ability to create new labels on-the-fly directly from the issue creation screen. No more jumping back and forth between settings and issue entry—if you need a new tag, just create it where you are.

What’s Next?

With the foundation of the UI and testing solid, we’re looking towards deeper integrations and performance optimizations in the next sprint. Stay tuned for more updates!

This post summarizes work from Pull Requests #52, #51, #48, #47, #46, and #33.