rabelenda opened a new issue, #9273: URL: https://github.com/apache/devlake/issues/9273
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement. ### Use case As an IT or engineering lead using [GLPI](https://github.com/glpi-project/glpi), I want DevLake to collect tickets so I can see throughput and lead time alongside the rest of our delivery data. DevLake has no GLPI data source. ### Description Add a GLPI plugin for the GLPI REST API (apirest.php). A scope is one GLPI entity. Child entities are separate scopes. Connection: * Endpoint: the GLPI base URL, for example https://glpi.example.com * Application token, from Setup → General → API * User token, from My settings → Remote access keys * Timezone, required, matching the GLPI server timezone. GLPI stores local times, and the plugin converts them to UTC The plugin opens a session with App-Token and Authorization: user_token, then sends App-Token and Session-Token on later calls. Domain mapping uses the ticket domain. Each entity becomes a board of type ITSM. Tickets are always collected: * Incident → INCIDENT, Request → TASK, any other type → TASK * New → TODO * Processing (assigned), Processing (planned), and Pending → IN_PROGRESS * Solved and Closed → DONE * Any other status → OTHER * Priority, urgency, and impact use GLPI’s scale: Very Low, Low, Medium, High, Very High, Major * The ITIL category is the issue component and an issue label * The requester is the issue creator * Due date is GLPI’s time to resolve * Lead time comes from GLPI’s solve delay * The issue URL points at front/ticket.form.php Time range: * A full sync lists tickets by opening date, newest first, and stops at the project time * An incremental sync lists tickets by last modification, newest first, and stops at the previous watermark Optional ticket data, chosen per scope. Assignees are on by default. The others are off: * Assignees: assigned users and groups on the issue, and as issue assignees * Follow-ups: public ITIL follow-ups as issue comments. Private follow-ups are skipped * Tasks: ticket tasks with a recorded duration as issue worklogs * Change logs: ticket history as issue changelogs * Solutions: the latest solution text is appended to the issue description * Ticket links: linked, duplicate, parent, and child links as issue relationships. A parent link also sets the parent issue Referenced users and groups are stored as accounts. This is not a full user or group directory sync. Plugin fields stay on the tool ticket as JSON. They are not written to the domain custom-field tables. Config UI: beta plugin, connection form, entity scope picker, and the optional-collection checkboxes. Collected entity: TICKET. Dashboards: MySQL (glpi-dashboard) and PostgreSQL (glpi-dashboard-pg). They show issue throughput, delivery rate, status distribution, and lead time. This version collects tickets for a GLPI entity. It does not collect assets, computers, changes, problems, projects, or the knowledge base. ### Related issues _No response_ ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
