Service projects
See which service projects and request areas were included in the scan.
Request Integrity for Jira Service Management
In Atlassian Marketplace reviewBring JSM request configuration into clearer view.
Request Integrity scans supported Jira Service Management request configuration and identifies objective configuration-integrity findings.
Current status
Submitted for Atlassian Marketplace review
Request Integrity is not being presented as publicly available or approved. No Marketplace installation link is provided while review is underway.
Overview
A consistent way to review request configuration.
Jira Service Management request configuration can become difficult to review consistently as projects, request types, fields, portal organization, and configuration evolve.
Request Integrity turns that configuration into a repeatable scan. It helps administrators see objective findings, understand what the scan covered, and return to earlier results when configuration changes.
What it reviews
Request experiences, from project coverage to fields.
The scan covers specific areas of Jira Service Management request configuration.
Request types
Review request types, their request configuration, and how they are organized for the portal.
Fields
Inspect field configuration in the context of the request experience where it appears.
From scan to follow-up
Context for reviewing and revisiting findings.
Findings stay connected to scan coverage, settings, and possible next steps.
Findings
Objective configuration issues
Rules produce findings tied to the request configuration that was reviewed.
Scan coverage
Know what was included
Coverage information gives administrators the scope needed to interpret a scan accurately.
History
Return to earlier scans
Scan history preserves useful context for reviewing results over time.
Guidance
Understand possible remediation
Findings include remediation guidance to support an administrator's own review and decision.
Baselines and change detection
Compare later scans with an accepted baseline.
An accepted baseline provides a point of comparison for later scans, making supported configuration changes easier to spot.
Run a scan
Review findings, coverage, and relevant configuration context.
Establish a baseline
Use reviewed configuration as a point of comparison for later scans.
Notice later change
Review configuration changes that appear in later scan results.
Control and context
Settings for the environment being reviewed.
Not every rule or configuration area has the same relevance in every service environment.
Settings and exclusions let administrators adjust scan behavior and document intentional exceptions, while scan history keeps earlier results available for review.
Currently in Atlassian Marketplace review
Ask about Request Integrity.
For questions about current scope or Marketplace review status, contact Gardiner Software directly.