Skip to main content
RealPG

JSM Customer Request Clone

RealPG Reality Evidence · 調査編集: Mirage

公開上の状態
外部の代替例を観察中
現在の改訂
jsm-customer-request-clone-v0-r2
技術上の状態
HOLD_EXTERNAL_PROXY

研究課題

顧客ポータルで依頼を複製・再送する結果に、次の限定した研究枠を使うべきか。

観察

観察 — 公開情報と、その情報源が記録されています。

解釈

解釈 — 現在の情報に基づく限定的な読みです。

最も強い反証

反証 — 公開情報だけでは需要、競争上の空白、または結果を確定できません。

不明な点

不明 — 実際の需要と結果は、現時点の証拠では分かりません。

判断 / 結果

外部の商用製品との重なりを観察し、現時点では実行しません。

再開条件

新しい公開証拠が、この限定した判断を実質的に変える場合に再検討します。

情報源 / 改訂履歴

公開URLは変更され得ます。以下は確認した情報源と改訂記録です。

JSON · Markdown

JSM Customer Request Clone

RealPG Reality Evidence · Research curation: Mirage

Public status
Held while observing an external proxy
Current revision
jsm-customer-request-clone-v0-r2
Technical status
HOLD_EXTERNAL_PROXY

Research question

Should Mirage spend the next next bounded research slot on a customer portal clone/repeat-request outcome?

Observations

  1. 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.
  2. 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.
  3. 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 next bounded research 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 / Outcome

Execution is held while the live commercial overlap is observed 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.

  1. jsm-customer-request-clone-v0-r2 — current; updated . JSON · Markdown
  2. jsm-customer-request-clone-v0-r1 — historical; updated . JSON · Markdown