serroba opened a new pull request, #9023: URL: https://github.com/apache/devlake/pull/9023
### Summary Adds a datasource plugin for [incident.io](https://incident.io), an incident management platform (same category as the existing PagerDuty/Opsgenie/Rootly plugins). Closes #9018. - **Connection**: Bearer-token auth against `https://api.incident.io/` - **Scopes**: incident types (`v1/incident_types`), with remote-scope listing - **Collection**: incidents via `v2/incidents` (cursor pagination); `test`/`tutorial` mode incidents excluded at extraction - **Conversion**: ticket-domain issues with type `INCIDENT`, feeding the existing DORA incident↔deployment correlation; `Declared at` → created date, `Resolved at` (fallback `Closed at`) → resolution date; retrospective incidents keep their resolution date even when it precedes declaration - Includes unit tests, e2e snapshot tests, config-ui registration (placeholder icon, not the brand mark), and a Grafana dashboard adapted from Rootly's ### Testing Beyond the unit/e2e suites, the plugin was validated end-to-end against a production incident.io workspace using the in-memory test server from `DevelopmentManual.md`: 50 real incidents collected, extracted, and converted with field-level verification against independently ingested reference data. That testing surfaced (and this PR includes fixes for) the v1-vs-v2 `incident_types` endpoint and the retrospective-incident timestamp ordering. ### Other information Docs for `Configuration/Incidentio` will need a companion PR to the website repo — happy to follow up with it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
