Skip to main content
addly

A public roadmap that explains why, never when.

Each item describes concept work, scope, rationale, and its last review. States express an exploration level; none is a Marketplace delivery promise.

Scope

Roadmap for the showcase and undistributed concepts. The displayed date is the last review date, never a delivery target.

A filterable path, not four columns of promises.

Permanent links preserve the app and state. Every item points to the limitation that motivates it, the documentation to inspect, and changes already visible in the concept.

Filter the register

8 items visible out of 8.

Readiness for JiraConcept work in progress

roadmap-readiness-states

Make off-happy-path states verifiable

Define empty, recoverable-error, and insufficient-permission states in the concept, with expected result and observable limitation.

Scope
Showcase and evaluation protocol · Jira issue panel
Last review
· no delivery date
Rationale
A pre-purchase decision needs as much visibility into recovery as into the primary scenario.
Portfolio InsightsConcept work in progress

roadmap-portfolio-permissions

Prototype cross-project reading boundaries

Write a test matrix that distinguishes visible, partially visible, and inaccessible initiatives.

Scope
Authorization concept · cross-project Jira project page
Last review
· no delivery date
Rationale
Useful aggregation must never broaden access to the issues that feed it.
Context LinkerConcept work in progress

roadmap-context-permissions

Define the suggestion-filtering protocol

Cover combined Confluence and Jira access before treating a relationship as presentable.

Scope
Authorization concept · Confluence context panel and Jira links
Last review
· no delivery date
Rationale
A suggestion must reveal neither the title, excerpt, nor existence of inaccessible content.
Readiness for JiraProposed priority

roadmap-readiness-manifest

Align permissions and retention with a testable manifest

Replace showcase intentions with scopes, flows, and durations from an architecture that has actually been selected.

Scope
Technical concept preparation · manifest and data
Last review
· no delivery date
Rationale
A security review cannot rely on a permission list that is independent from the distributed code.
Page SummaryProposed priority

roadmap-summary-templates

Establish a Confluence page and template matrix

Name the content variants to test, their restrictions, and expected macro behavior.

Scope
Concept compatibility · pages, templates, and space restrictions
Last review
· no delivery date
Rationale
A single demonstration page cannot support a general compatibility claim.
Portfolio InsightsUncommitted horizon

roadmap-portfolio-calculations

Document a reproducible calculation convention

Associate every health state with its source data, threshold, rule, and rerunnable test dataset.

Scope
Product hypothesis · health and dependency rules
Last review
· no delivery date
Rationale
A portfolio indicator is defensible only when an administrator can explain its output.
Page SummaryHypothesis to investigate

roadmap-summary-processing

Qualify explainable processing before choosing a provider

Compare local processing, deterministic rules, and a remote service on traceability, data, and human validation.

Scope
Architecture exploration · page summary
Last review
· no delivery date
Rationale
The provider must not be chosen before the need, expected evidence, and data constraints.
Context LinkerHypothesis to investigate

roadmap-context-index

Qualify permission-aware remote search

Define sources, freshness, deletion, and relevance measurement before indexing anything.

Scope
Architecture exploration · relationship search
Last review
· no delivery date
Rationale
A useful suggestion does not justify an opaque index or access broader than the reader’s permissions.
Reading rule: order and state may change after review. A changelog entry describes only an observable concept change; it proves neither Marketplace availability nor a commercial commitment.

A request becomes a chain of evidence.

  1. 01ObserveDescribe the problem and current workaround.Feedback
  2. 02QualifyLink the idea to an app, scope, and rationale.Roadmap
  3. 03ChallengePublish the limitation that still prevents a conclusion.Limitations
  4. 04EvolveTrace what actually changed in the concept.Changelog
  5. 05DocumentUpdate verification and related evidence.Documentation

What the last review means.

  • 01The scope and rationale were reviewed on that date.
  • 02The state may be revised without announcing a deadline.
  • 03A concept trace is not a Marketplace release.
  • 04A future delivery must link version, documentation, and verifiable behavior.

An idea is not a promise. A change leaves a trace.

Use the roadmap to understand the next verification, then the changelog to inspect only what actually changed in the concepts.