- Overview
- Getting started
- User guide
- Admin guide
- Requester and owner guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
Project Blueprints for Jira — Documentation
Project Blueprints for Jira lets the right people request new Jira projects (spaces) from blueprints that a Jira administrator has approved. Naming and key rules are checked while the requester types. A Jira administrator approves an exact preview, and the app then creates the project, sets it up and verifies the result. Every project it creates gets an owner and a review date, and a hash-chained ledger records who requested it and who approved it. It is published by Matify and runs entirely on Atlassian's Forge platform inside your Jira Cloud site; no data leaves Atlassian.
The main benefit: project managers and team leads no longer need the Administer Jira permission to get a new project, and Jira admins no longer set up projects by hand.
Jira is renaming "projects" to "spaces" in parts of its interface. This documentation says "project"; it means the same thing.
What it does
- Blueprints: capture a company-managed software or business project as a blueprint (scheme set, roles and members, components, versions, selected project properties, project-scoped field contexts), or create a team-managed blueprint from Jira's built-in Kanban or Scrum template.
- Requests: people who hold the Request projects (Project Blueprints) global permission request a project in three steps, with live checks against your naming and key policy and Jira's own key and name rules.
- Approval: a Jira admin approves an exact preview of what will be created (optionally a second, different Jira admin). Requesters can't approve their own requests, unless you allow Jira admins to approve their own requests (off by default).
- Provisioning and verification: the app creates the project, adds role members, components, versions, field contexts and properties, then re-reads the project and compares it with the plan.
- Catalog: every project on the site, how it was created (through the app or outside it), its owner, review date, activity and flags.
- Owners and reviews: owners confirm that their projects are still needed, recommend archiving, or hand ownership over.
- Ledger and exports: an append-only, hash-chained record of every request, approval and provisioning run, plus CSV and JSON exports for audits.
What it doesn't do
- It doesn't block projects created directly in Jira. Jira has no hook for that. The app detects them and marks their origin as "Outside the gate".
- It doesn't create or copy boards, filters, dashboards, automation rules, work items or the priority scheme.
- It doesn't copy, edit or delete schemes. New projects share the blueprint's schemes.
- It never deletes, trashes, archives or renames projects or other Jira content. The only thing it removes: in exact role mode, Jira's default role members on a project the app has just created.
- It doesn't provision service projects (Jira Service Management), Jira Product Discovery or customer service projects. They appear in the catalog only.
- It sends no e-mail. Optional tracking work items let Jira's own notifications inform people.
Details: Known limitations.
Pages in this documentation
- Getting started: installation, the first minutes, the "Get started" checklist, the guided test request, your first real request
- User guide: concepts and every page of the app, exports, Health and the settings table
- Admin guide: blueprints, policies, approvals, tracking work items, the catalog, the kill switch, data, and the partial provisioning runbook
- Requester and owner guide: requesting a project, following a request, owner reviews, the project Governance page
- Permissions and security: the seven scopes in plain words, what the app user can do, how the app limits that power
- Privacy and data: what is stored, where, for how long, and how to delete it
- Large sites: catalog scan, rate limits and what comes first
- Troubleshooting: every error code and common situations
- FAQ
- Known limitations
- Changelog
Requirements
- Jira Cloud. Project Blueprints is installed into Jira.
- Installing needs a Jira site administrator.
| Who | Where | What they can do |
|---|---|---|
| Jira administrators (Administer Jira) | Jira settings → Apps → Project Blueprints | Everything: blueprints, policies, approvals, catalog, ledger, Health, settings |
| Holders of Request projects (Project Blueprints) | Apps → Project Blueprints → Request a project | Request projects from the blueprints available to them (once requests are open) |
| Every Jira user | Apps → Project Blueprints → My requests, My projects | See their own requests and the projects they own; confirm reviews |
| Project administrators (Administer projects on a project) | Project settings → Governance | See how the project was created, its owner and review date; request an owner change |
The app checks these permissions on the server for every call, not only in the menu. Non-admins never see the full catalog.
Installation
- Open the Project Blueprints for Jira listing on the Atlassian Marketplace (or search for it in Jira under Settings → Apps) and start the free trial.
- Review the permissions Jira asks you to approve. They are explained in Permissions and security.
- Open Jira settings → Apps → Project Blueprints. The admin pages appear in Jira's admin sidebar: Overview, Approvals, Blueprints, Policies, Catalog, Ledger, Health, Settings.
After installation nothing is requested or created. Requests are off, and the Request projects (Project Blueprints) permission is granted to nobody. The catalog scan starts by itself shortly after installation. Continue with Getting started.
Licensing and trial
- Paid through Atlassian, with a 30-day free trial. Sites with up to 10 users are free.
- While the licence is active or in trial, everything works.
- While the licence is inactive, Project Blueprints is read-only: no new requests, approvals, provisioning or scans, and no changes to blueprints, policies or settings. Requesters can still withdraw open requests, and admins can still cancel them or close a partial one as it is. A provisioning that is already running stops before its next step; if the project already exists, the request becomes Partial and can be resumed once the licence is active again (within 7 days of the approval), otherwise it becomes Failed and nothing was created. The catalog, requests, ledger and exports stay readable, and a banner explains the state.
- The weekly maintenance run continues even without an active licence, so that personal-data reporting and the erasure of closed accounts go on.
Uninstalling
Before uninstalling, export what you want to keep (Ledger page → Exports, Catalog CSV). On uninstall, Project Blueprints writes an UNINSTALL entry to its ledger and asks Forge to cancel the job of each provisioning that is running. Such a provisioning can stop part-way, so that project may be partially set up.
- Projects, and everything the app wrote into Jira (role members, components, versions, field-context assignments, the app's project properties, tracking work items), stay in Jira.
- The Request projects (Project Blueprints) global permission disappears from Jira.
- The app's stored data stays in Atlassian's Forge hosted storage and is retained and deleted under Atlassian's Forge data lifecycle for uninstalled apps. A reinstall starts with empty app storage; the old data can be re-linked only on a request made within 21 days of the uninstall.
- To remove the stored data first, use Settings → Data → Delete all app data (also available when the licence is inactive). Details: Privacy and data.
Support
Email support@matifyapps.de, or use the login-free form or the public tracker linked from the support page. Include the diagnostics file from Health → Download diagnostics (it contains no names, e-mail addresses or project content), the error code and its reference ("ref"). Response times are in the Matify service level agreement.
Security issues: never in a public ticket. Email support@matifyapps.de with "security" in the subject.
More: Data security and privacy statement · Privacy policy · Terms