Omniscio

PM Cross-Entity Links

Bidirectional linking between a Mission Control item and any of 28 other kinds of thing in Omniscio — vault notes, mind maps, diagrams, whiteboards, flowcharts, URLs, writer documents, email threads, meetings, sessions, PM items, Tasks V2 tasks, Team Chat messages and channels, GitHub pull requests, commits, branches and issues, Mission Control goals, documents, spreadsheets, forms and dashboards, projects, calendar events, shares, tracker issues and plugin work. Links are made from either side through a search-and-select picker, shown on the item and on the linked tool, and unlinked rather than destroyed.

On this page

What it is

Bidirectional linking between Mission Control board items and other entities in the app -- vault notes, mind maps, diagrams, whiteboards, flowcharts, URLs, writer documents, email threads, meetings, sessions, PM items, Tasks V2 tasks, Team Chat messages and channels, GitHub PRs, commits, branches, and issues, Mission Control goals, documents, spreadsheets, forms and dashboards, projects, calendar events, shares, tracker issues and plugin work (28 entity types).

Where to find it

The Mission Control item card shows a Links tab listing all linked entities grouped by type, and each linked tool shows backlink chips in its header. Users create links from a tool's toolbar via a search-and-select picker (PmItemPicker), and can unlink from either side.

How it behaves

A PM item can be linked to any of 28 stored entity types (27 you can create; the old diagram type is kept so existing rows still read, and nothing creates it). Each link row shows the target's current title, falling back to the saved name, and finally to "<kind> (name unavailable)" - never a bare code. Clicking a link opens the exact session, note, mind map, Writer document, email, meeting or item; web addresses and GitHub links open in the browser. Team Chat and whiteboard links show their name but have no page to open yet. A meeting from another provider is saved as granola:<id> (or zoom:, fireflies: and so on): it keeps its name on the Links tab and does not open an in-app page. The Add link button on the Links tab adds a web address (http or https only), a GitHub issue (owner/repo#number), another board item, a project (pick it from your project list), a calendar event (paste the Omniscio event link from your agenda or a reminder), a share (paste its share link) or a tracker issue (jira:PROJ-42, linear:ENG-7; Asana, Trello, ClickUp, Notion, Airtable and Monday too); the last three also ask for a name. A project opens itself, a calendar event opens on its calendar, and a share opens in the share viewer; each keeps the name you gave it, and calendar names never call Google. A Linear issue opens on linear.app and a Jira issue opens on your connected Jira site; other trackers, or Jira with no site connected, show their name with no open button. Plugin work links (from Decks, Storyboard Planner, PRD Stack, LMS, Newsletter Builder or Calendar Scheduler) show their name and open that plugin's panel. Mission Control goals, documents, spreadsheets, forms and dashboards open inside Mission Control from the item's Links tab. They are linked from the other side: each of those pages has ⋯ > Link to item, which searches your board items and links the open page to the one you pick. A link to a goal, document, spreadsheet or form that was deleted is hidden until it is restored, and a link to a Tasks V2 task is hidden once that task is finished (Tasks files completed work rather than deleting it, so a finished task counts as gone from the item's point of view) — restore the task and the link returns on its own. A task link shows under a Tasks heading on the Links tab and opens Tasks on that task. The other direction works too: a task's Add context menu offers Project item, which attaches a Mission Control item to the task. GitHub entities navigate to GitHub URLs (validated https://github.com/ prefix) rather than activating an in-app project. GitHub commit links can be created automatically by the commit scanner when a commit message references an MC item (e.g. "MC-42"). GitHub PR links are discovered by a 5-minute polling scanner that parses item references from PR titles and bodies.

No dedicated settings. Requires missionControlEnabled.

The items being linked are described in mission-control.md, the parent system for this area. Two neighbours worth knowing: pm-session-link.md connects a running session to an item rather than a document or a code artifact, and pm-search-integration.md makes those same items findable from global search. The tools on the other end of a link are covered by kms.md for vault notes, mindmap.md, whiteboard.md and flowchart.md for the plugin surfaces, and ai-writer.md for writer documents. Every page in this library is listed in INDEX.md.

Last verified 2026-10-29