Architecture decision
Connect the decision to the relevant project and issues.
The panel brings surrounding context into a dedicated area so the document stays readable and its links remain verifiable.
The guide remains separate from the hero so the demonstration, instructions, and report have room to work as a complete evaluation space.
The steps direct observation; they do not automatically detect your actions.
Enter “PROJ-248” in the simulated Confluence panel search.
Observe: The list is reduced to items whose labels match the local search.
These notes stay on this page and are not sent to any service.
0/1,200
Step 1 of 3: Filter suggested relationships.
Demonstration interface and data. Host-product controls are rendered with Atlaskit; no app is installed.
Every use case begins with an observable friction, then shows the expected change without promising an unmeasured result.
Connect the decision to the relevant project and issues.
Keep the brief, risks, and Jira tracking within reach of the page.
Show related documents without cluttering the content.
A feature is credible only when its state, source, and next action remain readable.
Suggestions start from the page and remain subject to user confirmation.
Projects, issues, decisions, and documents retain an explicit role.
Relationships stay accessible without interrupting reading.
The trust profile separates verifiable facts, expected controls, and material still to produce for this concept. It implies no certification or availability.
Open the trust profileUntil the app is published, we display neither a plan nor a commercial estimate. The Pricing page explains the licensing model and will link to the official Atlassian Marketplace calculator.
Understand licensingThese questions are specific to the concept. The published version must align with the real manifest, hosting model, and limitations.
A real implementation must filter every search using the signed-in person’s Confluence and Jira permissions.
Suggestions may be assisted, but the prototype requires explicit confirmation before a relationship is created.
The intended configuration separates manual search, suggestions, and space rules so administrators keep control.
Every step keeps the context of Context Linker. The quick start, documentation, trust profile, and evaluation record form one journey instead of a collection of generic links.
Reproduce this app’s preset, controls, and limitations.
Open the labInstallation, configuration, permissions, and verification.
Read before installingConnect permissions, data, and missing evidence to this app only.
Examine the evidenceShare the scenario, compatibility, and limitations in a printable format.
Open the datasheetExport evidence, limitations, and blockers specific to this app.
Assemble the recordUnderstand concept changes and how they relate to known limitations.
View the changesNo published note explicitly carries this app yet. The app-specific resources above remain the reliable source; the site does not manufacture editorial recommendations.
This product is still a demonstration: no Marketplace link, price, review, or installation is invented. Until an official URL exists, the pilot-access brief remains locally copyable and can be submitted only when compliant data collection is enabled.