Project Templates for Jira guide
This guide describes the tested development workflow. Marketplace approval is pending; public installation has not been announced. Use an authorised development installation.
1. Capture accessible work
Open the app from Jira Apps. Use an existing company-managed Jira Software project and an Epic you can currently access. Enter its key and capture the accessible Epic, Tasks or Stories and Subtasks.
Capture creates no Jira work. Permission-filtered search does not establish that every hidden child was included. Templates remain private to their creator in the current installation, and runs create work only in the same project.
2. Save a private revision
Name and save an immutable revision. Summaries and supported description text can use variables such as {{Client}}. Add optional responsibility labels such as Owner; the source assignee account is not automatically copied.
Use an explicit source anchor to derive signed due-date offsets, or leave dates unset. Calendar dates use date-only arithmetic. Editing a description in the plain-text editor replaces its previous rich formatting. Unsupported mentions, media and cards are omitted with notice.
3. Select branches and supply inputs
Open the revision and select parents before descendants. Excluding a parent excludes its children. Supply variables and roles only for selected pending work.
Choose currently assignable people. Explicit Unassigned is available only when the current project default supports it and the assignee field is not required. There is no substitute-person fallback or administrator fallback.
Supply supported required custom fields. Plain text, finite numbers, dates and current single-select options are supported. Complex required fields or inaccessible values block the run. The app does not bypass Jira screens or permissions.
4. Review the frozen preview
Acknowledge omissions and normal Jira notifications, defaults and automation. Review resolved summaries, descriptions, supported fields, assignees and dates. Any input change invalidates the preview; it expires after ten minutes.
Confirm once. Native queued work can continue as the initiating Jira account after the tab closes, with current permissions. Reopen saved runs after an interrupted connection rather than starting a replacement run.
5. Inspect progress and save a receipt
Review counts and freshly accessible output keys. Prepare a receipt, then choose Save prepared file within thirty seconds. At preparation time, the authorised file is already in the browser; protect any downloaded copies. Later revocation cannot erase a copy you already saved.
Cancellation stops future work when detected. An already dispatched request may still complete. Created Jira work is not rolled back, and failed readback holds remaining work instead of recreating known output.
6. Recover within the existing run
Correct pending inputs applies to a paused run with a confirmed rejection and no unresolved dispatch. Previously created work is retained. Resume safe work reuses the same run.
For an uncertain create, inspect Jira and verify a known matching key or ID. The attempt marker and native output must verify. Search absence is not evidence that a create failed. Never blindly retry an uncertain create; contact support if the evidence remains unresolved.
Data residency
The app stores its persistent data in Forge SQL. In-scope data comprises private template content, captures, previews, run plans, owner and mapped account IDs, and operational attempt and receipt records persisted there. Transient compute, platform operational logs, customer-downloaded CSV files, separate support correspondence and this marketing website are outside this app’s storage-residency commitment.
Storage follows the host Jira app’s supported Atlassian residency location. Atlassian handles Forge SQL pinning and migration with the host app, without a separate app region setting. Compute can execute in another location. See the privacy notice’s residency scope and Atlassian’s Forge guidance.
Limits and maintenance
The current bounds are 100 selected work items per tree, 100 private revisions per installation, ten distinct role labels per revision, ten temporary captures, a 96 KiB resolved plan, 100 retained runs or previews, and ten attempted creates per item. A tree above the supported limit is rejected rather than silently treated as complete.
Use Check scheduled maintenance to remove eligible expired records. Unsaved captures expire after thirty minutes. Eligible run content expires ninety days from creation. See the privacy notice for erasure, account reporting and uncertain-dispatch quarantine.
Attachments, comments, workflow/status copying, shared templates, project creation, cross-project/site copies, arbitrary rich-content fidelity and complex custom-field types are not supported.
For help, include the app version or environment, a run reference and the visible error code. Do not send credentials, tokens, complete work-item exports or sensitive screenshots. Contact [email protected].