⚠️ Check request is valid.

• My request is about the Tasks plugin for Obsidian.
• I am only requesting a single feature in the Tasks plugin. Multiple changes should be split into individual requests, with links between them.
• I believe my requested feature will be generally applicable to other Tasks plugin users, not just me: it is not uniquely tied to my personal workflow.

⚠️ Please check that this feature request hasn't been suggested before.

• I searched previous Tasks plugin Ideas in Discussions didn't find any similar feature requests.
• I searched previous Tasks plugin Issues didn't find any similar feature requests.

🔖 Feature description

Add the ability to move a task (and its subtasks) from one file/section to another file/section directly from the Tasks UI.

Currently, if a user wants to move a task to a different file or section, they must:

1. Copy the task manually
2. Navigate to the destination file
3. Paste the task in the correct location
4. Return to the original file
5. Delete the original task

This is tedious, especially for users who frequently reorganize their tasks as projects evolve.

✔️ Solution

Add a "Move" button (↔️) next to the existing Edit (📝) and Postpone (⏩) buttons in query results. When clicked:

1. A filterable modal appears showing all files/sections that contain tasks (respecting the Global Filter)
2. Files are sorted by last modified date (most recent first)
3. Each file shows its sections with task counts
4. Full folder paths are displayed to avoid ambiguity (e.g., Daily Notes/2024/01/15)
5. Selecting a destination moves the task (and any indented subtasks) to the end of that section
6. The original task is deleted from its source location

Additionally:

• Add the same option to the inline editor suggestion dropdown as the last item, allowing users to move tasks while editing
• Settings option to exclude certain folder paths from the destination list
• hide move button query instruction to hide the button when not needed

❓ Considered (and discarded) alternatives

• Drag and drop: More intuitive but significantly more complex to implement across different views
• Separate plugin: Considered, but deep integration with Tasks (Global Filter, query results, editor suggestor) makes this better suited as a core feature
• Command palette only: Less discoverable and requires more steps

📝 Additional Context

Related issues:

• Optional automatic action upon task completion: move task to an archive file #2855 (Move task to archive on completion) - automatic move on completion
• Optional automatic action upon completion: move a task to a "completed tasks" list within the note #2856 (Move task to completed list within note) - automatic move within same note

This feature differs by providing manual, user-initiated moves to any destination, not just completion-triggered archiving.

I have a working implementation ready for PR if this feature is accepted.