Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

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

Ouverte
  • Quelque chose ne va pas ?
#9,273 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

@rabelenda y travaille déjà.

Depuis le 28/10/2026.

  • #9275 par @rabelenda — ouverte

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
38/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
go
Domaine
data-engineering

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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
Langage dominant
Go
Étoiles
3.2k
Forks
830
Merge moyen
2 j 12 h
PR mergées (30 j)
61

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/devlake

Toutes les issues de apache/devlake

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.