Project Templates for Jira
Turn a repeatable Epic into your next work plan.
Project Templates for Jira helps teams reuse onboarding and release work inside an existing company-managed Jira Software project. Capture an accessible Epic, its Tasks or Stories and their Subtasks; save a private revision; choose branches; fill in text variables; map responsibilities to people; and review the exact work before creating it.
Work is created in the same project. The app does not create Jira projects, copy project configuration or transfer work to another project or site. Templates are private to their creator in the current installation.
Capture a private revision
An immutable revision keeps your reusable work tree separate from each run. Capturing does not create Jira work. Capture follows current source access: permission-filtered results do not prove that hidden children were included.
Choose the work you need
Select parent branches and their descendants, substitute text variables and assign responsibility labels to currently assignable people. Use an explicit source anchor to move calendar due dates, or leave dates unset. A source assignee’s account ID is not automatically copied.
Review before creating
Review resolved summaries, supported descriptions, fields, assignees and dates before confirmation. Input changes invalidate the frozen preview, and previews expire after ten minutes. Jira screens, required fields and current permissions still apply.
Mentions, media, cards and other unsupported content are omitted with notice. Normal Jira defaults, notifications and automation can affect the output. Editing a description in the plain-text editor replaces its previous rich formatting.
Follow an honest creation record
Confirmed work continues through the native Forge queue after the browser closes, using the initiating Jira account’s current permissions. Reopen the saved run to inspect progress, cancel future work and prepare currently authorised output keys.
A confirmed rejection can allow correction of pending inputs within its existing paused run. An uncertain create is held and never blindly resent. Search absence does not prove a create failed. A dispatched request can still complete after cancellation; the app does not roll back work already created in Jira.
Current v1 bounds
- 100 selected work items per tree and 100 private revisions per installation.
- Ten distinct responsibility labels per revision and ten temporary captures.
- A 96 KiB resolved creation plan and 100 retained runs or previews.
- Ten attempted creates per item.
These are bounded product limits, not unlimited storage or a performance guarantee. Attachments, comments, workflow or status copying, shared templates, project creation, cross-project/site copies and complex custom-field types are outside this release.
Availability and questions
The app has been submitted to Atlassian Marketplace and approval is pending. Public installation and pricing have not been announced.
Read the workflow guide or contact [email protected]. The privacy notice describes Forge processing and retention; the terms explain use and review responsibilities.