Board movement as captured behavior
Show where a kanban card was meant to land
Keep source column, scroll position, and destination feedback visible when documenting card movement in your product.
- ✓Drop indicators lag behind the pointer
- ✓Horizontal scrolling hides context
- ✓Canceled drags leave artifacts
Card-movement evidence with a landing point
A visible intended destination
Show the column boundary and landing indicator that explain an ambiguous drop.
Cancellation with defined cleanup
State what must disappear and what must remain when a drag is abandoned.
Movement separated from automation
Keep visual placement concerns distinct from saved status and downstream workflow effects.
Set up a board with visible constraints
Card movement depends on column position, scroll state, and the intended destination. In your product, prepare a sample board with several columns, a horizontally hidden destination, long card titles, and one restricted transition if the product supports it. Capture the source card and column headings before dragging. Record the expected movement rules and account role separately. This is a review of your board interface, not a promise that Retick provides kanban workflow automation.
Preserve the drag and drop sequence
Record picking up a card, scrolling toward the destination, hovering between two cards, and dropping. Include a canceled drag as a separate sequence. A distinctive issue is Drop indicator stays in the old column while the pointer reaches the next one. Show the column headings and pointer path so reviewers can understand the intended landing area. Avoid claiming the saved status changed incorrectly when the recording only shows ambiguous placement feedback.
Agree on a visible landing contract
Use Retick browser capture or upload supported screenshots and recordings. Inspect AI candidate issues, edit inferred workflow effects, reject unsupported persistence claims, and annotate the stale drop indicator. Example acceptance criteria: the indicator identifies the current permitted destination; canceling removes the indicator and leaves the original card visible; and the completed move gives an understandable final location. Have product approve behavior at column boundaries and any restricted transition message before treating those details as requirements.
Revisit other movement methods
After implementation, manually repeat with an empty destination, a crowded column, and the product's alternative move control where available. Test keyboard behavior directly instead of inferring it from pointer footage. Verify saved ordering, permissions, and downstream automation through your application's own tests. Retick does not move customer cards, run transition rules, or inspect hidden board state. Use fictional task titles and exclude private project information before capture; automatic redaction should not be assumed.
Download the reviewed findings for a file handoff, or export selected issues from the individual media item to a connected Trello board and list. That export is a destination for reviewed issues, not synchronization of the kanban board being examined. Include the source column, intended destination, and scroll condition in the task.
Review a kanban drag sequence
Show the starting column, destination feedback, and final board state.