Interactive
Local search and filtering
Interactive across the three fictional labels.
Link a page to its context with confirmation
Filter three fictional relationships, confirm a link, trigger the no-results state, then restore the initial preset. This quick start covers an interface and demonstration data: it is not an installation, a compatibility test, or Marketplace evidence.
Confluence · Context panel8 to 12 minutes
Expected output
An exportable observation, not an automatic score.
Reset restores the fictional preset. Your observation and verdict stay local until you explicitly copy them.
What you will build
Page-to-project context
Filter three fictional relationships, confirm a link, trigger the no-results state, then restore the initial preset.
Read product limitationsPrerequisites before you click
- An example page whose project, decision, or document context is currently hard to find.
- The expected authorization rule between Confluence spaces and Jira projects.
- The relationship type that must remain explicit to avoid ambiguous links.
- No real identifier to enter: use PROJ-248 or the suggested fictional labels.
The initial preset is documented and restorable.
You know exactly what is already displayed before the action. ‘Reset all’ restores those values without retaining your trials.
- STATE 01
Three fictional relationships are suggested and PROJ-248 is selected.
- STATE 02
Search is empty and no relationship has been confirmed.
- STATE 03
The panel queries neither Confluence nor Jira and creates no remote relationship.
One action, one expected result, no decorative step.
Instructions use only controls present in the demo. If a behavior is not interactive, it appears below as blocked evidence.
- 01
Filter the project relationship
Enter ‘PROJ-248’ in search.
Expected result
The local list narrows to the matching project relationship.
- 02
Confirm the relationship
Select the visible result, then activate ‘Link selection’.
Expected result
A confirmation precisely names the relationship added to this demonstration page only.
- 03
Test the no-results state
Replace the query with a term that is not present.
Expected result
An explicit empty state replaces the list and the linking action becomes unavailable.
- 04
Restore the preset
Use Reset in the panel, then record the need for deletion and permission controls.
Expected result
All three choices return, PROJ-248 is selected again, and the previous confirmation disappears.
lab Confluence
Use the preset, then keep the trace.
The guide does not monitor your clicks; it tells you what to observe. Reset, observation, verdict, and Markdown export remain under your control.
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.
Record the local result
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.
Verification recipe
‘Blocked’ means this demo cannot produce the evidence. It means neither failure nor compliance of the future product.
Interactive
Confirmation before linking
Interactive; no relationship is added without an explicit action.
Interactive
No-results state and reset
Interactive without reloading the page.
Blocked evidence
Cross-product permissions, remote deletion, and suggestion quality
Not testable in this fixed list; blocked evidence before publication.
Troubleshooting and limitations
The first diagnostic separates a misunderstood local action from a capability that simply does not exist in the showcase.
Why is Link selection unavailable?
The current selection must remain visible in the filtered results. Clear the query or choose a result that is present.
Does the relationship persist after reset?
No. Reset removes the local confirmation. No data is stored outside the component.
Can I verify permissions on a real page?
No. The demo shows the interaction model; host-permission filtering must be proven with a real implementation and manifest.
This quick start tests a concept in the browser. Before a pilot, require a real listing, manifest, compatibility, permissions, data processing, contract, and support channel.
Open the shareable datasheetThe quick start ends with a traceable decision.
Add the exported observation to the packet, assign the blocked evidence, and decide whether to continue, ask, pause, or reject.