Skip to main content

    Filter by idea status

    Filter by product

    4862 Ideas

    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.

    Board Relationship Graph ViewOpen

    One feature that could significantly improve large-scale knowledge organization in Miro would be an automatically generated relationship view between boards.Today, it is already possible to create connections between boards by inserting links inside elements (cards, sticky notes, shapes, text blocks, etc.). When clicking these links, users can navigate directly to another board — and sometimes even to a specific element inside that board.The idea is for Miro to recognize these links as relationships and automatically generate a visual graph view of connected boards.This would work similarly to the graph visualization available in Obsidian, where notes become connected through links.How it could work: Every board becomes a node in the graph. Links between boards become edges/connections. The number of links between two boards could increase the visual strength/thickness of the connection. The graph could optionally support relationship weighting based on the frequency of references between boards. Users could filter by workspace, project, team, tags, or board type. The graph could support zooming, clustering, and relationship exploration. Additional possibilities: Show inbound and outbound links (backlinks). Identify highly connected boards (knowledge hubs). Detect isolated boards with no relationships. Visualize architecture, processes, product discovery, or organizational knowledge structures. This feature would be especially powerful for: Product teams System architecture mapping Service design Enterprise knowledge management Research and discovery workflows Process modeling Complex project ecosystems Today, many teams already use Miro as a visual knowledge platform, not just as a whiteboard. A relationship graph would make hidden structures visible and transform disconnected boards into an interconnected knowledge network.The key value of this feature is that links would stop being just navigation elements and would become meaningful structural relationships between boards and knowledge domains.This could become one of the most powerful organizational, discovery, and navigation capabilities in Miro for large environments.