Early Access for Jira Service Management admins
Know when your JSM request flows break — before your users do.
Request Sentinel runs controlled synthetic checks against important Jira Service Management request types, then shows whether each flow still behaves as expected.
No demo call required. Early Access is designed for JSM admins who prefer written, self-service evaluation and setup.
The problem
JSM request processes can fail silently.
Service desks evolve. Request types, permissions, workflows, automations and integrations change. A process that worked yesterday can stop behaving correctly today.
Configuration drift
Field and request-type changes can make a customer-facing flow invalid.
Permission changes
Portal access or visibility changes can block the users who need the request type.
Late detection
The first signal should not have to be a real user saying the process is broken.
How it works
Controlled checks for important request flows.
1. Choose a process
Select a Jira Service Management service desk and request type.
2. Define expectations
Set the expected initial status and validate required fields.
3. Run synthetic checks
Request Sentinel creates controlled synthetic requests on a schedule.
4. Review results
See Healthy/Failed status, run history and sanitized diagnostics.
Current capabilities
Built for a focused early-access workflow.
Use cases
Start with one safe request process.
IT access requests
Check whether users can still submit access-related service requests.
Employee onboarding
Monitor the intake request type that starts onboarding work.
Automation-heavy flows
Detect when a request no longer starts in the expected state.
Early Access should begin with a dedicated or non-critical request type before expanding to more important flows.
Trust and safety
Designed to minimize data movement and operational surprises.
Forge-hosted
Request Sentinel is built on Atlassian Forge with Forge-hosted storage and compute. Deployment tooling has reported Runs on Atlassian eligibility, but no public badge is claimed here.
No remote backend
The product currently has no external business-data backend, remotes or external business-data egress.
Real request side effects
Synthetic checks create real Jira Service Management requests. They may trigger notifications, SLAs, automations, approvals, webhooks or integrations.
Early Access
Apply for a written, self-service pilot.
Early Access is limited and intended for Jira Service Management admins or platform owners who can evaluate Request Sentinel with written guidance. Participants help shape onboarding, monitoring defaults and future pricing.
FAQ
Practical answers before you apply.
What is Request Sentinel?
A Forge app that monitors selected Jira Service Management request flows using controlled synthetic requests.
Does it create real Jira requests?
Yes. Synthetic checks create real Jira Service Management requests.
Can synthetic requests trigger automations or emails?
Yes. They may trigger notifications, SLAs, automations, approvals, webhooks and integrations.
Do I need a call to get started?
No. Early Access is designed around written, self-service setup and asynchronous support.
Where is data stored?
Product data is stored in Forge-hosted storage. The app currently has no external business-data backend.
Can I disable monitoring?
Yes. Monitors can be disabled, and disabled monitors do not run automatically.
Can I delete Request Sentinel data?
Yes. The app includes an administrative app-data deletion control.
Does deleting Request Sentinel data delete Jira requests?
No. Jira issues created by synthetic checks remain in Jira.
Is Early Access free?
Early Access terms will be communicated before activation. Permanent free access is not promised.
Does Request Sentinel send external alerts?
Not yet. Early Access focuses on automatic checks, status, history and diagnostics.
What happens if a check fails?
The monitor shows Failed and provides sanitized run diagnostics to help identify the failure stage.