IDVerse incident
3rd Party System - Atlassian Jira Experiencing Degraded Service
IDVerse experienced a minor incident on April 18, 2025 affecting 3rd Party Component Services, lasting 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Apr 18, 2025, 05:06 PM UTC
The IDVerse Support Portal is currently experiencing degraded performance due to an active incident with one of our third-party service providers, Atlassian Jira. The issue, identified by Jira, is impacting issue search and filter functionality across all Jira Software customers. As a result, access to the IDVerse Support Portal and support tickets may be delayed or temporarily unavailable. Atlassian has identified the root cause and is actively working on a resolution. We are closely monitoring their progress and will update the status of this incident as more information becomes available.
- resolved Apr 18, 2025, 05:58 PM UTC
The issue impacting access to the IDVerse Support Portal has been resolved. Incident Summary: Between 02:00 UTC and 16:30 UTC on April 18, 2025, a third-party incident with Atlassian Jira affected our support systems. During this time, the Sprint field was not visible in issue views, and issue search/filters showed an empty Sprint field cell for some Jira customers, including our portal. The root cause was a recent code change introduced by Jira. They've deployed a fix to resolve the issue, and services have been verified as fully recovered.