Skip to main content
addly
Confluence · Context panelConcept to evaluate

Context LinkerFind related projects and decisions without leaving the page.

The panel brings surrounding context into a dedicated area so the document stays readable and its links remain verifiable.

Guided demonstration

Test a realistic scenario, then preserve the record.

The guide remains separate from the hero so the demonstration, instructions, and report have room to work as a complete evaluation space.

Guided demonstration journey

The steps direct observation; they do not automatically detect your actions.

Step 1 of 333% of the guide displayed

Filter suggested relationships

Enter “PROJ-248” in the simulated Confluence panel search.

Observe: The list is reduced to items whose labels match the local search.

addly Context

Connect this page

Demonstration data · Controls rendered with official Atlaskit components.

Record the local result

These notes stay on this page and are not sent to any service.

0/1,200

Local verdict

Step 1 of 3: Filter suggested relationships.

Demonstration interface and data. Host-product controls are rendered with Atlaskit; no app is installed.

Host product
Confluence
App placement
Context panel
Primary audience
Knowledge, delivery, and governance teams
Commercial state
Marketplace listing to connect

The moments when this app earns its place.

Every use case begins with an observable friction, then shows the expected change without promising an unmeasured result.

01

Architecture decision

Connect the decision to the relevant project and issues.

02

Launch file

Keep the brief, risks, and Jira tracking within reach of the page.

03

Knowledge base

Show related documents without cluttering the content.

What the team sees. What it can explain.

A feature is credible only when its state, source, and next action remain readable.

01

Contextual search

Suggestions start from the page and remain subject to user confirmation.

02

Typed links

Projects, issues, decisions, and documents retain an explicit role.

03

Side context

Relationships stay accessible without interrupting reading.

Compatibility

Distributed app version
No app version is distributed
Latest compatibility verification
Never — no versioned build exists to test
Technical support status
Unverified — no supported host or app version range
View the matrix

Permissions required

  • Read the current page
  • Search permitted spaces
  • Read Jira only for accessible projects
Examine security

Data handling

  • Demonstration relationships
  • No remote indexing active
  • Host permissions still need validation
Trace the flow

Evidence follows the app, not the sales pitch.

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 profile

Official pricing will remain in the right place.

Until 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 licensing

Questions to resolve before installation.

These questions are specific to the concept. The published version must align with the real manifest, hosting model, and limitations.

Can the panel expose private pages?

A real implementation must filter every search using the signed-in person’s Confluence and Jira permissions.

Are links created automatically?

Suggestions may be assisted, but the prototype requires explicit confirmation before a relationship is created.

Can suggestions be disabled?

The intended configuration separates manual search, suggestions, and space rules so administrators keep control.

The final step must lead to the official listing.

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.