- Overview
- Getting started
- User guide
- Admin guide
- Requester and owner guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
Changelog
2.1.0 — Initial release
First public release of Project Blueprints for Jira. The Marketplace shows it as version 2.1.0 (the Forge version). Inside the app, the diagnostics file and the provenance property of each created project use the product version 1.0.0; both refer to this release.
- Company-managed blueprints captured from a software or business reference project: scheme associations (permission, notification, issue security, work type, work type screen, workflow, field scheme or legacy field configuration scheme), roles and members, components, versions, selected project properties and project-scoped field contexts found by a background scan of all custom fields. Fidelity report ("Will apply" / "Won't apply") before activation.
- Team-managed blueprints from Jira's built-in Kanban or Scrum template, with the lead (who becomes the project's administrator) and governance properties.
- Blueprint settings: allowed requester groups, lead and owner rules, additive or exact role mode, additional role members, components and versions, category, one or two approvals, review interval, description template. Versions on re-capture; pending requests stay pinned to their version.
- Naming & key policies (key pattern combined with Jira's key rule, key and name templates, name pattern, reserved keys, key length) with a live tester, and metadata forms (text, number, date, single select, user).
- Request a project in three steps for holders of the new Request projects (Project Blueprints) global permission, with live key and name validation, Jira's key suggestions and key reservation. My requests with progress, withdraw and request similar.
- Approvals of an exact dry-run preview by a Jira admin, optionally a second, different admin; lead confirmation; reject with reason; expiry (14 days by default); stale-preview protection; decision lock; self-approval setting (off by default).
- Provisioning and verification in the background: journaled, idempotent steps with automatic retries, verification against the plan (Verified, Verified with notes, Partial, Failed), Retry remaining steps within 7 days of the approval, Leave as is and close, Stop after current step.
- Catalog of every project on the site with origin (Governed, Outside the gate, Pre-existing, Adopted), owner, review date, activity and flags; detection of projects created outside the gate with their creator from Jira's audit log; bulk actions that write only the app's own project property.
- Owners and reviews: My projects with Still needed, Recommend archive and Transfer ownership; the project settings Governance page with Request owner change.
- Optional tracking work items and review reminder work items in one admin-chosen project (off by default).
- Ledger: append-only, hash-chained record with integrity check.
- Exports: evidence report, catalog, requests, reviews (CSV) and ledger (CSV and JSON), built in the browser and safe against formula injection.
- Health: catalog scan, rate-limit points, queues, failed steps, capture errors, permission-check mode, probes, diagnostics download.
- Guided first run: Get started checklist and a one-time guided test request.
- Safeguards: requests off and the request permission granted to nobody on install, kill switch, permission checks as the app with a fail-closed fallback, write-path contract.
- Privacy: people stored as account IDs only (no names, avatars or e-mail addresses), retention settings, weekly personal-data reporting, erasure of closed accounts, free-text redaction, Delete all app data.
- Runs entirely on Atlassian's Forge platform; no data leaves Atlassian.