# JSM Customer Request Clone

**Status:** HOLD_EXTERNAL_PROXY

## Question

Should Mirage spend the next Stage A execution slot on a customer portal clone/repeat-request outcome?

## Observations

- Atlassian issue JSDCLOUD-7817 describes a long-running customer request to clone or repeat portal requests and remains unresolved with Gathering Interest.
- Recurring Requests & Templates for Jira Service Management lets customers repeat an existing request, schedule it, or save it as a template.
- Forge exposes a customer-portal request-view action that supports customer and unlicensed accounts.

## Interpretations

The live commercial overlap is treated as an external proxy rather than a new Stage A execution slot.

## Strongest 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.

## Unknowns

A small current Marketplace install count does not prove either strong or weak demand. The decision changed execution priority; it did not retroactively prove the original problem unreal.

## Decision

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.

## Freshness

Case and sources were checked 2026-08-31T00:00:00Z and are CURRENT.

## Sources

- [Atlassian issue JSDCLOUD-7817](https://jira.atlassian.com/browse/JSDCLOUD-7817)
- [Recurring Requests & Templates](https://marketplace.atlassian.com/apps/3762836664/recurring-requests-templates-for-jira-service-management)
- [Forge portal request-view action](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-service-management-portal-request-view-action/)

## Source observation

The current issue, commercial Marketplace listing, and Forge documentation were independently re-opened on 2026-08-31. The bounded source-backed observations remain recoverable; install count is not treated as market-size evidence.

Public URLs are mutable; the source observation identifiers, retrieval time, source-reported dates or versions where available, and verification record the observation event. This is not source-body archival or cryptographic preservation.

## Revision

Current revision: `jsm-customer-request-clone-v0-r2` ([immutable revision](/reality/revisions/jsm-customer-request-clone-v0/r2.md)). This r2 is a provenance audit, not a new Product outcome; [r1 remains historical evidence](/reality/revisions/jsm-customer-request-clone-v0/r1.md).