What Jira returns
Phrase results returned by Jira’s API, using your current permissions. These are observations in that context.
For Jira Service Management
Review Jira Service Management
request-type content.
Review your request-type catalog before you change it. Bring your phrases. See what the checks actually tell you.
Live on Atlassian Marketplace
Phrase to review“password reset”
01 / Observed
Request type returned
An API response in the current Jira user context.
02 / Configuration
Description is blank
A deterministic check for missing request-type wording.
03 / Advisory
Review related wording
A heuristic suggestion, for your judgment.
Synthetic illustration. Not a live report or a customer portal search.
01 Read-only Jira requests
02 One accessible desk per run
03 Changes stay in your hands
Know what you are looking at
Three kinds of evidence.
Three different meanings.
What the checks flag
Deterministic findings, including blank descriptions and duplicate names. Review the configuration behind each finding.
What to consider
Transparent typo and synonym heuristics offer wording suggestions for manual review. A suggestion is not proof.
The app does not reproduce customer visibility or portal ranking, and does not guarantee findability or ticket deflection.
Before. After. Understand.
A repeatable review,
on your terms.
For service owners and administrators reviewing a changing request-type catalog.
Read the setup and usage guide ↗Select a desk. Bring your phrases.
Review one accessible service desk in your current Jira context.
Read each finding in context.
Keep API observations, configuration checks and advisory suggestions separate.
Compare complete snapshots.
Active-license features enable local exports and compatible snapshot comparison. Changes do not automatically mean improvements.
Start with the details
Understand the workflow.
Know its limits.
Install through the public Atlassian Marketplace listing. A 30-day trial is available for teams of all sizes.