Support
Service Project Standards for JSM is supported by Matify. One address, read by a person.
Before you write
Check the documentation first — it covers what the app compares, where each
screen lives, and what the app deliberately does not verify (SLA configuration, automation rules, portal
settings, customer permissions, JSM Forms fields and issue security scheme association are all outside
what any read-only app can check today, and the reason is stated for each).
Ask a question or report a problem
What to include
- The Jira site type (company-managed vs. team-managed for the service project involved) and whether
the issue is in the site-wide admin console, a project's Standards check panel, or the dashboard gadget.
- Whether a scan was running, and, if so, its scan id from the Scan status screen.
- What you were doing, and what you expected instead.
- The diagnostics bundle from the admin console's Diagnostics screen. It contains only counts, codes
and scan metadata — no project name, no finding text, no account id resolved to a name.
What never to include
The tracker is public and its history stays readable after an edit. Never post a password, an API
token, an Atlassian account id, an email address, a project name, an exception's reason text, queue JQL,
or anything else your organisation would not publish. If a question cannot be asked without one, email it
instead.
Security vulnerabilities
Never a public issue. Email mira.maty@web.de privately, and
please do not include customer data or credentials in the report.