Matify/Project Blueprints for Jira

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

What it doesn't do

Details: Known limitations.

Pages in this documentation

Requirements

WhoWhereWhat they can do
Jira administrators (Administer Jira)Jira settings → Apps → Project BlueprintsEverything: blueprints, policies, approvals, catalog, ledger, Health, settings
Holders of Request projects (Project Blueprints)Apps → Project Blueprints → Request a projectRequest projects from the blueprints available to them (once requests are open)
Every Jira userApps → Project Blueprints → My requests, My projectsSee their own requests and the projects they own; confirm reviews
Project administrators (Administer projects on a project)Project settings → GovernanceSee 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

  1. 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.
  2. Review the permissions Jira asks you to approve. They are explained in Permissions and security.
  3. 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

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.

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