Skip to main content
addly

A known limitation should be easier to find than a sales argument.

No real product incident exists in this showcase. This register addresses each concept’s declared limitations, scope, workaround, and evidence still required.

Filter limitationsView status

Not an incident history

Each identifier describes a concept limitation or missing evidence—never an outage, an affected customer, or an invented fix.

Eight addressable limitations, linked to their path.

Filters remain in the URL. Every row has a stable permanent link and connects the concept, documentation, roadmap, and changelog traces that provide context—without claiming to resolve the limitation.

Filter the register

8 items visible out of 8.

Readiness for JiraDeclared limitation

limit-readiness-states

Not every off-happy-path state is interactive

The demo makes the primary verdict testable but does not yet simulate every empty, recoverable-error, or insufficient-permission state.

Scope
Local showcase · simulated Jira Cloud · issue panel
Last review
· no delivery date
Rationale
The concept first validates the verdict and its criteria; recovery states do not yet have a complete protocol.
Workaround
Record these states as blocked evidence in the evaluation packet and draw no conclusion about their behavior.
Readiness for JiraEvidence required

limit-readiness-manifest

The published manifest, retention, and scopes do not exist yet

The permissions shown describe the functional intent of the concept, not a Forge manifest or production processing.

Scope
Future architecture · permissions, storage, and data lifecycle
Last review
· no delivery date
Rationale
No versioned app is distributed and no remote production architecture has been selected.
Workaround
Evaluate the local scenario only and pause any purchase review until the matching technical evidence is published.
Portfolio InsightsEvidence required

limit-portfolio-permissions

Cross-project permission boundaries are not validated

The aggregated view uses fictional initiatives and does not yet prove that every issue is filtered according to real Jira access.

Scope
Local showcase · simulated Jira Cloud · cross-project project page
Last review
· no delivery date
Rationale
The prototype is not connected to a Jira tenant and cannot exercise a real authorization matrix.
Workaround
Limit evaluation to the summary composition and require permission testing in an isolated environment before any pilot.
Portfolio InsightsDeclared limitation

limit-portfolio-calculations

Indicators and thresholds rely on fictional data

The visible health states support evaluation of the page narrative; they are neither benchmarks nor production calculations.

Scope
Demonstration · health rules, dependencies, and decisions
Last review
· no delivery date
Rationale
No customer definition, historical source, or real calculation convention is provided to the showcase.
Workaround
Replay every rule with a documented test dataset and reject any score whose source or threshold cannot be explained.
Page SummaryDeclared limitation

limit-summary-processing

No analysis engine or AI provider is connected

The summary is demonstration data written to test hierarchy, sources, and human validation.

Scope
Local showcase · simulated Confluence · content macro
Last review
· no delivery date
Rationale
Processing, region, retention, and subprocessors have not been selected.
Workaround
Evaluate traceability and manual correction; infer no analysis quality, latency, or coverage.
Page SummaryEvidence required

limit-summary-templates

Compatibility with templates and page variants still requires testing

The concept shows a macro in one example page; it does not yet cover templates, restrictions, or varied content structures.

Scope
Future Confluence Cloud · pages, templates, and space restrictions
Last review
· no delivery date
Rationale
No versioned compatibility matrix exists before a testable Forge implementation.
Workaround
Treat the macro as a single placement and list every required page variant in the pilot protocol.
Context LinkerEvidence required

limit-context-permissions

Host-permission filtering of suggestions is not proven

The displayed relationships are fictional; the demo cannot verify that a suggestion remains hidden without Confluence or Jira access.

Scope
Local showcase · Confluence context panel · Confluence and Jira links
Last review
· no delivery date
Rationale
No host tenant or real permission graph is connected to the prototype.
Workaround
Evaluate explicit confirmation only and require cross-access tests before processing real content.
Context LinkerDeclared limitation

limit-context-index

No remote index or production search is active

Panel suggestions are demonstration relationships and measure neither relevance, coverage, nor freshness of an index.

Scope
Demonstration · relationship suggestion, typing, and confirmation
Last review
· no delivery date
Rationale
Search architecture, data, and governance are not yet defined.
Workaround
Test confirmation with manually entered links and retain the source of each relationship.

The format will change only when a real product exists.

A future confirmed issue will remain separate from a vulnerability and a service incident.

  • 01Verifiable product, hosting, version, and confirmation date.
  • 02Observable symptom, scope, and trigger conditions.
  • 03Tested workaround, side effects, and review owner.
  • 04Fix state without an invented delivery date.
  • 05Exact links to support, status, changelog, and corrected documentation.

A documented limitation protects better than an optimistic FAQ.

Open the relevant identifier, verify its workaround, and follow the linked work. A future outage belongs on Status; this register remains functional.

Choose an appView status