Matify/Project Blueprints for Jira

Requester and owner guide

This guide is for people who request new Jira projects (spaces), for project owners, and for project administrators. You find Project Blueprints in Jira's top navigation under Apps → Project Blueprints, with three pages: Request a project, My requests and My projects.

Requesting a project

Who can request

You can request a project when all of these hold:

Otherwise the page tells you why, for example "Project requests aren't open on this site yet" or "You don't have the 'Request projects' permission". Your own requests and the projects you own stay visible under My requests and My projects in every case.

You don't need the Administer Jira permission, and you won't normally see Atlassian's "Allow access" screen.

The three steps

1. Blueprint. Pick a blueprint from the gallery. Each card shows the project type and style, a short description, You'll get (what the new project receives), Won't apply (what isn't set up, for example boards or automation rules) and how many Jira admins must approve. Choose Use this blueprint.

2. Details.

FieldNotes
Project name (required)Checked against your site's naming policy and against existing project names. The expected format and an example are shown under the field
Key (required)Capital letters and digits, starting with a letter, 2 to 10 characters (your naming policy may narrow this range). A suggested key may be filled in from the policy
Project leadDepending on the blueprint: you, a fixed person, or a person you choose. A lead you choose becomes project lead and project administrator; the approving admin confirms this
OwnerDepending on the blueprint: you, the project lead, or a person you choose. The owner confirms periodic reviews
CategoryOnly if the blueprint lets you choose
Extra fieldsFields your admin added (for example client or cost centre). Required fields are marked
PurposeWhat the project is for, up to 2,000 characters. Helps the admin decide. Don't put personal data here

Name and key are checked as you type, against your site's policy and against Jira. Typical messages:

Continue to review becomes available when everything is valid. Otherwise the page lists what is still needed.

3. Review. Check the summary and read What happens next. Choose Submit request. You get a request ID and, if your admin turned tracking work items on, a link to a tracking work item. If another open request already uses the same key, the request isn't submitted and the page shows "Another open request already reserves the key ACME. Choose another key."

What happens next

  1. A Jira admin reviews your request and the exact plan. Nothing is created before they approve. Some blueprints need two different Jira admins.
  2. After approval, Project Blueprints creates the project from the blueprint and checks the result against it.
  3. Follow the status under My requests. The project link appears there when it is ready.

Requests that nobody approves expire after a while (14 days by default) and release the key.

Statuses you may see

StatusMeaning for you
Pending approvalWaiting for a Jira admin. You can withdraw it
Waiting for 2nd approvalOne admin approved; a second, different admin must approve too
ApprovedApproved; creation starts shortly
ProvisioningThe project is being created and set up. The progress shows "n of m steps done"
DoneYour project is ready. Choose Open project
Done with notesYour project is ready; some details differ from the blueprint (see the notes)
PartialThe project exists, but not everything was set up yet. A Jira admin is handling it
FailedThe project wasn't created. Nothing was created. Contact your Jira admin
BlockedCreation didn't start (for example an approver lost their admin rights). Nothing was created. Your Jira admin will tell you whether to submit again
RejectedNot approved. The reason is shown
WithdrawnYou withdrew it
ExpiredNobody decided in time
CancelledA Jira admin closed it without a decision

Notifications

Project Blueprints sends no e-mail. If your admin turned on tracking work items, a work item is created for each request in a project your admin chose, normally with you as reporter. Approval, rejection and completion are added there as comments, so you get Jira's usual notifications. Otherwise check My requests.

My requests

The table lists your requests with blueprint, key, name, status, progress, a link to the result and the tracking work item. Select a key to open the request: facts, the provisioning steps, the verification result and the timeline.

For project owners

The owner is the person who confirms, from time to time, that a project is still needed. Every project created through Project Blueprints gets an owner and a review date. A Jira admin can also make you the owner of an existing project.

My projects

My projects lists the projects you own with their review date and review status (Up to date, Review due, Review overdue, No review date), when they were last reviewed, last activity, origin and flags. A review is "due" when its date is within the next 30 days.

For each active project you can choose:

You can add an optional note to each. Notes are visible to Jira admins in the catalog and in the reviews export. Don't put personal data in them.

Reminder work items

If your admin turned on review reminders, you get one work item per week (on Mondays, UTC) in the tracking project, assigned to you, listing your projects that are due or overdue for review. Jira notifies you as usual. Confirm the reviews under My projects.

For project administrators: the Governance page

Project administrators (the Administer projects permission on a project) find Project settings → Governance. It shows:

Request owner change proposes a new owner with an optional note. A Jira admin confirms it in Project Blueprints; until then the current owner stays, and the page shows "Owner change pending".

If the page says the project isn't in the catalog yet, check again later; a new project is normally added within a few minutes.