Matify Service Project Standards for JSM

Terms

Publisher: Matify · Contact: mira.maty@web.de · Last updated: 18 September 2026 · © 2026 Matify.

Service Project Standards for JSM is licensed under the standard end user agreement Atlassian provides for Marketplace apps. You accept it when you install or subscribe to the app through the Atlassian Marketplace, and Atlassian renders its current text there.

Provider-specific terms

Matify adds only the following, each of which reflects something the app actually does.

  1. Read-only. The app's Jira permission set is 30 granular read: scopes plus its own storage scope and the personal-data reporting scope — zero write scopes, zero manage:* scopes, zero issue-content scopes. It cannot create, edit or delete a project, request type, field, queue, scheme, screen, role, component or issue, at any time.
  2. Findings are advisory, not automatic. When the app finds a deviation, it shows a plain-language summary and a rebuild checklist. Atlassian publishes no write API for request-type field layouts that would let any app safely make the change for you, so nothing the app reports is ever applied to your site automatically. You remain solely responsible for any configuration change in Jira.
  3. Coverage is stated, not implied. SLA configuration, automation rules, portal branding and settings, customer/portal permissions, fields that live in a JSM Form, issue security scheme association, and team-managed service projects are outside what the app can verify. This is stated in the product's Coverage tab and on every exported evidence pack. Nothing the app produces should be read as certifying compliance in an area it states it does not cover.
  4. Scans run at your direction. Scans run on a schedule an administrator controls, on a manual trigger by a Jira administrator, or automatically for a newly created service project. Matify does not initiate a scan of your site outside these paths.
  5. Support channel. Support is provided by email at mira.maty@web.de and through the public tracker linked from the support page. Please do not include credentials, personal data or confidential content in a support request.

What is not here

No limitation of liability, warranty disclaimer, governing-law clause or indemnity appears on this page. Those sit in Atlassian's standard agreement, and duplicating or varying them here would only create ambiguity about which text governs.