Matify Service Project Standards for JSM

Service Project Standards for JSM

Capture what one good service project looks like. Compare every other one against it. Know the moment any of them drift.

Published by Matify for Atlassian Jira Service Management Cloud. Read-only: the app never writes to your Jira or JSM configuration.

Documentation What the app compares, where everything lives, and how to read a finding. Security & privacy statement What the app reads and stores, how it is protected, and why it sends nothing anywhere. Privacy policy The formal policy for the data the app processes. Terms The terms that apply to using the app. Support How to ask a question, report a bug or request a feature.

What it does

  1. An administrator captures a standard from a reference service project: its request types, request form fields including hidden and preset ones, queues, schemes, screens, roles and components.
  2. The app compares every assigned service project against that standard, on a daily light scan, a weekly full scan, or on demand.
  3. Each project gets a score, and every deviation becomes a finding with a plain-language summary and a rebuild checklist.
  4. The change log records what moved between two scans — the record Jira itself does not keep for request types, fields and queues.
  5. Exceptions let an administrator accept a specific deviation with a reason, an owner and an expiry.

Trust

The app runs entirely on Atlassian's Forge platform and makes no external network calls of any kind. It holds no write scope, so it cannot change anything it reads. It stores configuration metadata and Atlassian account ids, never issue content, and it says plainly which configuration areas no public API lets it check.