Skip to main content

    Filter by idea status

    Filter by product

    4803 Ideas

    MichelNew Here

    Missing Metadata for Sidekick AI - Structural Context RequiredOpen

    Subject: Critical Missing Metadata for Sidekick AI - Structural Context RequiredProblem Summary: Sidekick AI currently lacks access to essential structural metadata about board organization, severely limiting its ability to assist with structured workflows, process diagrams, and organized boards. The AI can only see isolated object content, not the organizational logic users create.Specific Missing Capabilities:1. Frame Hierarchy & ContainmentSidekick cannot detect which objects are placed inside frames When a frame is selected, child objects (sticky notes, shapes, text) are not visible to the AI The AI cannot identify parent-child relationships in frame structures Use case impact: Swimlane diagrams, workshop templates, sectioned boards become invisible as organized structures2. Kanban Board Grid PositionFor 2D Kanban boards with rows and columns, Sidekick cannot identify which cell a card occupies When a card is selected, its column and row position are not provided The AI sees cards in isolation, not as part of a structured grid Use case impact: Process flows with departmental swimlanes (rows) and process steps (columns) cannot be analyzed or modified intelligently3. Spatial RelationshipsNo coordinate data (X/Y position on board) No relative positioning (above, below, left of, right of) No grouping or clustering information No proximity detection between objectsReal-World Example: I created a 2D Kanban board to map a business process:Columns: Process steps (1. Receive inquiry → 2. Create offer → 3. Review order → etc.) Rows: Departments (Sales, Warehouse, Certificates) Cards in cells: Specific tasks/responsibilitiesWhen I select a card containing "test2000" located in Column C, Row "test 1", Sidekick only sees:Content: "test 2000" Visual appearanceSidekick does NOT see:That it's in Column C That it's in Row "test 1" That it's part of a 2D Kanban structureWhy This Matters: Miro is fundamentally a visual, structural collaboration tool. Users organize information spatially and hierarchically. Without access to this organizational logic, Sidekick is reduced to a basic content editor that cannot:Understand process flows Analyze departmental responsibilities Recognize organizational patterns Provide context-aware suggestions Manipulate structured workflowsWhat Sidekick Needs:Frame metadata: Parent frame ID, list of child objects within frames Kanban grid position: Column name/ID, row name/ID for cards in2D boards Spatial coordinates: X/Y position, relative positioning to other objects Grouping data: Which objects are grouped together Connector relationships: Which objects are connected by lines/arrowsCurrent Workarounds (All Suboptimal):Color-coding objects instead of using frames Adding text tags to indicate position/category Using Kanban boards instead of frames (but even then, grid position is invisible) Manually explaining structure in every promptExpected Behavior: When I select objects on a structured board, Sidekick should understand:"This card is in the'Sales' row and 'Create Offer' column" "These5 sticky notes are inside the 'Brainstorming' frame" "This shape is connected to 3 other shapes via arrows" "These objects are grouped in the top-left quadrant"Impact: Without structural metadata, Sidekick's value is limited to simple content tasks (writing text, creating isolated objects). For knowledge workers using Miro for process mapping, project planning, workshop facilitation, and structured collaboration, the AI cannot meaningfully assist with the core organizational work.Request: Please prioritize exposing structural metadata to Sidekick. This is not a "nice-to-have" feature—it's fundamental to making AI useful in a spatial collaboration tool.

    Live Sync Between Mind Maps and Data TablesOpen

    This request proposes a native capability in Miro to link a mind map to a hierarchical data table with automatic, two-way synchronization. It targets teams that outline work in mind maps and track execution in tables, ensuring both views stay aligned without manual effort.Feature SummaryEnable a live, persistent link between a mind map and a corresponding hierarchical table. When the mind map’s nodes, hierarchy, or labels change, the linked table updates automatically to reflect the same structure and metadata.Use CaseA user builds a mind map to structure ideas, then converts it to a hierarchical table for planning and tracking. As the mind map evolves during collaboration, the table must stay synchronized so stakeholders can rely on the structured view for status, ownership, and reporting—without re-exporting or rebuilding.Current LimitationMind maps and tables are separate objects with no native linkage. After converting or exporting, updates to the mind map do not propagate to the table. Users must manually regenerate or edit the table, risking drift, duplication, and errors.Proposed SolutionAdd “Link to Table” when creating a table from a mind map (and vice versa). Maintain a live reference mapping nodes to table rows, including hierarchy and selected properties (e.g., title, tags, owner, status). Support real-time sync triggers on create, edit, reorder, move, merge, and delete actions in the mind map. Provide sync options: one-way (mind map → table) or two-way, with conflict resolution prompts. Include field mapping and column selection, plus the ability to pause/resume sync. Visual indicators show linked status and last sync time; audit log captures changes.BenefitsImproves workflow efficiency by eliminating manual regeneration. Reduces errors and duplication, maintaining a single source of truth. Preserves data consistency across views for planning and reporting. Supports dynamic project planning as structures evolve.