JSM Customer Request Clone
- Current status
- HOLD_EXTERNAL_PROXY
- Current revision
- jsm-customer-request-clone-v0-r2
- Freshness
- CURRENT
- Last verification
Research question
Should Mirage spend the next Stage A execution slot on a customer portal clone/repeat-request outcome?
Observations
- OBSERVATION — Atlassian issue JSDCLOUD-7817 describes a long-running customer request to clone or repeat portal requests and remains unresolved with Gathering Interest. Sources: jsm-issue.
- OBSERVATION — Recurring Requests & Templates for Jira Service Management lets customers repeat an existing request, schedule it, or save it as a template. Sources: jsm-marketplace.
- OBSERVATION — Forge exposes a customer-portal request-view action that supports customer and unlicensed accounts. Sources: jsm-forge.
Interpretations
INTERPRETATION — No current claim in this epistemic class.
Strongest counter
COUNTER — A live commercial Marketplace product has substantial exact overlap with the frozen clone/repeat-request outcome, so Mirage did not spend the next Stage A execution slot and treats the overlap as an external proxy instead. Sources: jsm-marketplace.
Unknowns
UNKNOWN — A small current Marketplace install count does not by itself prove either strong or weak demand. The decision changed execution priority; it did not retroactively prove the original problem unreal.
Decision
HOLD_EXTERNAL_PROXY — Do not spend the next Stage A execution slot; observe the live commercial overlap as an external proxy.
Reopen conditions
- The competitor gains meaningful usage and public evidence exposes a bounded unmet gap it does not solve.
- A platform change creates a materially different outcome not covered by the competitor.
- Customers or Atlassian expose a distinct requirement making the app unsuitable.
Source observations
Public URLs are mutable; source observation metadata records what Mirage checked, not cryptographic archival.
- jsm-issue
- Publisher: Atlassian. Role: Customer request issue. URL: https://jira.atlassian.com/browse/JSDCLOUD-7817. Retrieved: . Source state: unresolved-gathering-interest. Checked: . Verification: RECONSTRUCTABLE_FROM_CURRENT_SOURCE. Re-opened current issue; unresolved Gathering Interest state and customer-portal clone friction are recoverable.
- jsm-marketplace
- Publisher: Atlassian Marketplace. Role: Commercial product listing. URL: https://marketplace.atlassian.com/apps/3762836664/recurring-requests-templates-for-jira-service-management. Retrieved: . Source state: current. Checked: . Verification: RECONSTRUCTABLE_FROM_CURRENT_SOURCE. Re-opened current commercial listing; repeat, scheduled, and template behavior is recoverable.
- jsm-forge
- Publisher: Atlassian. Role: Forge module documentation. URL: https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-service-management-portal-request-view-action/. Retrieved: . Source state: current. Checked: . Verification: RECONSTRUCTABLE_FROM_CURRENT_SOURCE. Re-opened current Forge documentation; customer and unlicensed access is recoverable.
Revision history
r2 is a provenance/source-recoverability audit, not a new Product outcome.