Features go missing in the Kanban

[j2nm4y]

Features go missing in the Kanban

I'm using it to develop an iOS app, which is kind of working. As the agents can't test the iOS app, the features seem to end up in a code-complete state, and that leaves them in limbo. I can't see them in the kanban UI.

Using the tools AI it went off and clarified this.

**_The feature tracking database shows 0% completion, but this is misleading. The reason is that features cannot be marked as "passing" without Xcode/iOS Simulator testing - which the automated agent environment doesn't have access to.

In Reality - Code is Substantially Complete

Based on the progress report and codebase, here's what's code-complete (implemented but untested):_**

I can't go and test the features because I can't see the feature and know what to test.

Ideally, there may need to be an extra lane in the kanban. Code-Complete or Testing.

Maybe marking items that need manual testing. A button on those to mark as passed would be great.

[pressurecooker4u]

It sounds like the main challenge here is visibility and workflow for code-complete but untested iOS features. Your observation about adding an extra lane—something like Code-Complete / Testing—is spot on. Many teams run into the same issue when automated agents can’t fully validate features due to environment limitations, such as Xcode or the iOS Simulator.

A few practical suggestions:

Add a dedicated “Manual Testing Required” lane in the Kanban board. This keeps code-complete features visible and prevents them from getting lost in limbo.

Include a “Mark as Passed” button for manual verification. This simplifies updating the progress without needing to dive into the backend database.

Use tagging or color-coding to indicate which items require manual testing. That way, even if they’re not actively being tested, they remain clearly visible.

Think of it like using a Hawkins Pressure Cooker in the kitchen. Just as the cooker efficiently handles cooking only when the lid is closed and pressure is properly managed, a Kanban board works best when every feature is “contained” in a visible, clearly defined lane until it’s fully tested and verified. For reference, a Hawkins Pressure Cooker ensures nothing gets overlooked and every step is accounted for:
https://www.pressurecooker4u.com/shop/category/hawkins-pressure-cooker-2/

Adding these workflow adjustments should help your team track untested features more clearly and avoid confusion between code-complete and fully validated items.