Destination picking in context

Give folder move feedback an unmistakable destination

Keep source location, navigation position, and selected destination distinct when documenting a move dialog.

  • ✓Sibling branches reuse names
  • ✓Navigation leaves stale selection
  • ✓Disabled targets lack explanations

Move dialog feedback with a known path

Unambiguous destination paths

Preserve the parent context needed to distinguish folders that share a name.

Selection rules made explicit

Ask product to define navigation and selection before describing the required repair.

A bounded move report

Separate stale dialog labels from storage and permission questions requiring independent checks.

Start with a destination people can recognize

A folder move dialog must distinguish where an item currently lives from where it will go. In your product, prepare sample folders with repeated names under different parents, one long breadcrumb, and a destination that the current role cannot select. Capture the source folder before opening Move, then show browsing into the intended destination. Record the account role and viewport separately so the receiving team can recreate the conditions.

Capture navigation and selection together

Show opening a parent, highlighting its child, going back, and confirming the move. Pause on disabled destinations and any explanation offered beside them. A distinctive issue is Move button keeps the previous child name after navigating to a sibling branch. Include both the breadcrumb and the action label rather than only a cropped button. Separate confusing navigation from an observed permission message; the same screenshot does not prove an access control failure.

Agree on what confirmation means

Bring supported screenshots or a recording into Retick, including browser capture when useful. Review the AI candidate issues, edit the destination names, reject inferred storage failures, and annotate the stale action label. Example acceptance criteria: the destination breadcrumb and confirmation name agree; navigating away clears a selection that is no longer valid; and canceling leaves the source list visibly unchanged. Ask product whether selecting a parent also navigates into it, since that interaction contract must not be invented during review.

Follow the move beyond the dialog

On the updated build, manually repeat the sibling navigation with duplicate folder names, a deeply nested branch, and no available destinations. Check the resulting success message and return navigation. Confirm actual placement and authorization with your application checks outside Retick. Captured media cannot verify filesystem transactions, prevent circular folder structures, or establish every role's rights. Use synthetic folder names and exclude private paths before recording because this process does not automatically redact them.

Download approved findings as a file handoff, or send selected issues from the individual media item to a connected Trello board and list. Review the destination path in the handoff so developers investigate the intended branch instead of another folder with the same name.

Capture the next folder move concern

Show the branch, selection, and action before preparing the handoff.