Project Templates for Jira terms
Read these app-specific details alongside the company Terms.
Last updated: October 24, 2026.
AvanSaber Inc. publishes Project Templates for Jira. These app-specific terms are read together with the AvanSaber Terms of Service, the AvanSaber privacy policy and the app privacy notice. Contact [email protected] for service questions.
Availability
The app has been submitted to Atlassian Marketplace and approval is pending. Public installation, pricing and commercial availability have not been announced. This website does not offer a checkout or request payment.
Any future paid availability, trials, seat counts, changes, cancellations and refunds will follow the published Marketplace offer and applicable Atlassian purchasing policies. No numeric price, free commercial tier, trial entitlement or custom refund guarantee is created by this page.
Authorised use and supported scope
An authorised Jira account with current project permissions is required. The supported workflow uses an existing company-managed Jira Software project, private creator-owned revisions and same-project work creation. It does not create projects, copy project configuration, share templates or transfer work across projects or sites.
Users review the frozen preview and remain responsible for source access, selected branches and people, required fields, Jira settings, normal notifications, automation effects and exported copies. Current Jira screens and permissions still apply. Hidden source work may not be included in capture.
Attachments, comments, workflow or status copying, arbitrary rich-content fidelity and complex custom-field types are outside the supported scope. Unsupported content is omitted with notice or blocks the run where necessary. Do not misuse access, share credentials, bypass controls or process information without authority.
Limits, creation and recovery
The v1 bounds are 100 selected work items per tree, 100 private revisions per installation, ten role labels per revision, ten temporary captures, a 96 KiB resolved plan, 100 retained runs or previews, and ten attempted creates per item. These are product bounds, not an uptime or performance guarantee.
Maintenance, native API limits and unavailable permissions or licences can pause new writes. Receipts and safe cancellation remain subject to current authorisation. A dispatched request can complete after cancellation is requested. Existing Jira work is not rolled back.
An uncertain create is held and never blindly resent. Search absence does not establish failure. Correct pending inputs and resume safe work only within an eligible existing run, following the guide. The service does not guarantee exactly-once native API outcomes or complete capture of hidden content.
Privacy, support and changes
The privacy notice explains Forge processing, retention, account reporting, erasure and exported-copy responsibilities. App erasure does not delete native Jira work already created.
Service, warranty, liability and dispute provisions follow the linked company terms alongside applicable Atlassian requirements. This page adds no separate support-resolution time, round-the-clock service, jurisdiction or liability amount.
We update these resources when the supported service or processing changes and provide notice where required. Contact support without sending credentials, tokens, complete work-item exports or sensitive screenshots.