Project Blueprints for Jira
Governed project requests for Jira. The people you allow request new projects (spaces) from blueprints your admins approved; a Jira administrator approves an exact preview; the app sets the project up, verifies it and records who requested and who approved.
- DocumentationGetting started, admin, requester and owner guides, troubleshooting and known limitations.
- Security & privacy statementWhat the app reads and stores, where it lives, and the permissions it needs.
- Privacy policyThe policy for the data the app processes.
- SupportAsk a question, report a bug or request a feature.
What it does
- Blueprints are captured from your own company-managed projects: scheme associations, roles and members, components, versions, category, selected properties and project-scoped field contexts. A fidelity report says what will and won't be applied.
- Requests: people who hold the "Request projects (Project Blueprints)" global permission request a project through a form that checks your naming, key and metadata rules while they type.
- Approval: a user who holds Administer Jira at that moment approves an exact preview; a second, different approver is optional.
- Provisioning and verification: the app creates the project, sets it up step by step and verifies it against the plan.
- Catalog: every project on the site with owner, review date, last activity and policy flags, including projects created outside the app.
- Ledger: requests, approvals and provisioning steps are kept in a hash-chained record with an integrity check and exports.
Trust
Requests are off and the request permission is granted to nobody until a Jira admin decides otherwise. The app never deletes or archives projects. It runs entirely on Atlassian's Forge platform, keeps its data in Forge hosted storage on your site, sends nothing outside Atlassian and stores Atlassian account ids, never people's names. Boards, filters, dashboards and automation rules are not created or copied; see the known limitations.