Matify/Project Blueprints for Jira

Terms — Project Blueprints for Jira

Project Blueprints for Jira is licensed under the standard end user agreement that Atlassian provides for Marketplace apps. You accept it when you install or subscribe to the app through the Atlassian Marketplace, where Atlassian shows its current text.

Provider-specific terms

Matify adds only the following. Each describes something the app actually does.

  1. Projects are created only after approval by a Jira administrator of your site. Project Blueprints creates a Jira project only for a request that a Jira administrator of your site approved after seeing a preview of the project — or two different administrators, if your administrators require two approvals. Requests are closed until your administrators open them, and nobody holds the permission to request projects until your administrators grant it. Your administrators decide which blueprints can be requested, who may request them and who approves.
  2. What the app creates in Jira is your data and stays. Projects the app creates and everything it writes into your Jira site — project settings, role members, components, versions, field-context assignments, project properties and optional tracking work items — are your organisation's Jira data. They remain in Jira when you uninstall the app or delete its data. Export the evidence you need before uninstalling.
  3. The app never deletes or archives projects. Project Blueprints never deletes, moves to trash, archives or renames a project, scheme or work item in Jira, and never edits existing work items. The only removal it makes is of role members that Jira adds by default to a project the app has just created, when the blueprint uses exact role mode; the approval preview shows this removal step. If a project was only partly set up, it stays as it is; your administrators can retry the remaining steps or remove the project themselves in Jira.
  4. Fidelity is limited to what Jira's APIs allow, and the app reports the result. Project Blueprints sets up projects through Atlassian's public Jira Cloud REST APIs. Some settings cannot be created or copied — for example boards, filters, dashboards and automation rules. They are listed in the Known limitations and in the fidelity report each blueprint shows before it can be activated, and the preview shows what will apply before a request is approved. After every provisioning the app re-reads the new project and reports what matches the plan. Review the preview and the result before relying on a new project.
  5. Support. Support is provided by e-mail at support@matifyapps.de, through the login-free support form and the public tracker linked from the support page, under the Matify service level agreement. Do not include credentials, personal data or confidential content in a public ticket.

What is not here

No limitation of liability, warranty disclaimer, governing-law clause or indemnity appears on this page. Those are in Atlassian's standard agreement; repeating or changing them here would only create doubt about which text applies.

Publisher: Matify · Contact: support@matifyapps.de · Privacy policy · Data security and privacy statement