Jira Service Management incident

Lookup Objects in Automation for Jira Service Management are not functioning

Major Resolved View vendor source →

Jira Service Management experienced a major incident on May 6, 2026 affecting Automation for Jira, lasting 1h 41m. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 09:35 AM UTC
Resolved
May 06, 2026, 11:17 AM UTC
Duration
1h 41m
Detected by Pingoru
May 06, 2026, 09:35 AM UTC

Affected components

Automation for Jira

Update timeline

  1. investigating May 06, 2026, 09:35 AM UTC

    We are investigating reports of lookup objects in Automation for Jira Service Management are not functioning as expected. Our engineering teams are actively investigating and working to resolve the issue. We will provide further updates in next 1 hour.

  2. monitoring May 06, 2026, 10:18 AM UTC

    A fix has been implemented to address the failures observed in the lookup objects within JSM Automation. We are actively monitoring the situation to ensure stability. We will share the final update within next 1 hour.

  3. resolved May 06, 2026, 11:17 AM UTC

    The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers.

Looking to track Jira Service Management downtime and outages?

Pingoru polls Jira Service Management's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Jira Service Management reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Jira Service Management alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Jira Service Management for free

5 free monitors · No credit card required