- Overview
- Getting started
- User guide
- Admin guide
- Requester and owner guide
- Permissions and security
- Privacy and data
- Large sites
- Troubleshooting
- FAQ
- Known limitations
- Changelog
FAQ
What does Project Blueprints do? It lets the right people request new Jira projects (spaces) from blueprints a Jira admin approved. Naming and key rules are checked live, a Jira admin approves an exact preview, and the app creates, sets up and verifies the project. Every project gets an owner and a review date, and a hash-chained ledger records who requested and who approved it.
Can it stop admins from creating projects directly in Jira? No. Jira offers apps no hook that runs before a project is created, so the app can't block or change projects created natively. It detects them: they appear in the catalog as "Outside the gate", with their creator from Jira's audit log where available, in Overview and in the evidence report.
Does it copy boards, filters, dashboards, work items or automation rules? No. Board and board configuration, filters, dashboards, automation rules, work items, attachments, comments and the priority scheme are not created or copied. The blueprint's fidelity report and the requester's gallery card list what won't apply. See Known limitations.
Does it change our schemes? No. New projects share the blueprint's schemes, like Jira's "share settings" option. The app never copies, edits or deletes a scheme. A later change you make to a shared scheme affects every project using it, as usual in Jira.
Why does the app need Jira-admin-level scopes? Creating a company-managed project requires the Administer Jira permission, and Jira has no narrower scope for it. With manage:jira-configuration and manage:jira-project, Jira gives the app user admin-equivalent rights. The app limits their use: requests are off by default, the request permission is granted to nobody, only admin-activated blueprints can be used, a current Jira admin approves an exact preview, and there is a kill switch, a ledger and a write-path contract. See Permissions and security.
Can a requester become a Jira admin through it? No. The app never grants global permissions or changes group membership. A request can make someone project lead and, through the blueprint's roles, a member of the new project's roles (for example its Administrators role). That is project-level only, the preview shows it, and when the lead isn't the requester, the approving Jira admin must confirm it.
Do requesters need Administer Jira? No. That is the point of the app. They need the Request projects (Project Blueprints) global permission, which you grant to groups.
Can two admins approve? Yes. Set Approvals required to "Two different Jira admins" on a blueprint (or as the default for new blueprints in Settings). The second approval must come from a different Jira admin than the first, and the requester can't approve their own request unless self-approval is turned on (see the next question).
We have only one Jira admin. Can we still use it? Yes. Turn on Allow Jira admins to approve their own requests (Settings → Approvals) by typing ALLOW SELF-APPROVAL. Each self-approval needs the project key typed and is recorded in the ledger as a self-approval.
Who sees the catalog? Only Jira admins. Owners see the projects they own under My projects; project administrators see one project's details on its Governance page. Non-admins never see the full catalog.
Who gets notified about requests? Project Blueprints sends no e-mail. If you turn on tracking work items, the app creates a work item per request in one project you choose and comments on approval, rejection and completion, so Jira's own notifications reach the people involved. Requesters can always follow their requests under My requests.
What happens if provisioning stops halfway? The request becomes Partial with the exact list of what exists and what is missing. A Jira admin can retry the remaining steps (Retry remaining … steps for KEY) within 7 days of the approval, or Leave as is and close. The app never deletes a partially provisioned project; you can move it to trash in Jira yourself. See the Admin guide.
Does it work with service projects? Service projects (Jira Service Management) appear in the catalog, but they can't be blueprints and can't be provisioned. Portal settings and request types aren't covered. The same applies to Jira Product Discovery and customer service projects.
Does it work with team-managed projects? Partly. A team-managed blueprint starts from Jira's built-in Kanban or Scrum template and applies the lead (who becomes the project's administrator) and the app's governance properties. It can't copy a team-managed project's configuration, because Jira has no API for that. Team-managed projects can't be captured as blueprints.
We're on Jira Enterprise and have Jira's own project templates. Why use this? Project Blueprints works on any Jira Cloud plan. On Enterprise, the added value is the governance around project creation: requests from people without admin rights, live naming and key rules, approval of an exact preview by one or two admins, a catalog of every project with owners and review dates, detection of projects created outside the gate, and a hash-chained ledger and evidence report for audits.
Does any data leave Atlassian? No. Project Blueprints runs entirely on Atlassian's Forge platform. It has no external domains, no remote back end, no web triggers and no analytics or telemetry service. Exports are built in your browser. See Privacy and data.
What does Jira's audit log show? Jira's audit log names the app as the creator of projects made through it, because the app creates them in the background. The ledger, the project's provenance property and the Governance page record who requested and who approved.
Is there a free tier? Sites with up to 10 users don't pay for the app. Every other site gets a 30-day free trial and then pays through Atlassian. While the licence is inactive the app is read-only.
What happens on uninstall? Projects and everything the app wrote into Jira stay. The app writes a final UNINSTALL ledger entry and asks Forge to cancel the job of each provisioning that is running; such a provisioning can stop part-way. The request permission disappears from Jira. Stored data is retained and deleted under Atlassian's Forge data lifecycle for uninstalled apps. Export the ledger and evidence report first. See README.
How long does provisioning take? It depends on the size of the blueprint and on Jira's rate limits. The request page shows each step as it runs. Approved provisioning has priority over the app's background work.