Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature][Plugin] Add a GLPI data source plugin

Abierto
  • ¿Algo no está bien?
#9,273 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

@rabelenda ya está trabajando en esto.

Desde el 28/10/2026.

  • #9275 de @rabelenda — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
data-engineering

Línea de trabajo

The issue specifies a GLPI REST API plugin, entity scopes, ticket collection, optional ticket data, and MySQL and PostgreSQL dashboards, but names no source files or tests. Start by reading the repository’s existing data source plugin implementations and their tests to find the plugin entry points and conventions. Done means collecting tickets for a GLPI entity with the described mappings and options, plus the config UI and dashboards.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

type/feature-request
Search before asking
  • I had searched in the issues and found no similar feature requirement.
Use case

As an IT or engineering lead using 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?
  • Yes I am willing to submit a PR!
Code of Conduct
Lenguaje dominante
Go
Estrellas
3.2k
Forks
832
Merge medio
2 d 6 h
PR fusionados (30 d)
62

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/devlake

Todos los issues de apache/devlake

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.