[Feature][Plugin] Add a GLPI data source plugin
メンテナーはふだん 2 日以内に返信
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 38/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- go
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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
- I agree to follow this project's Code of Conduct
- 主要言語
- Go
- スター
- 3.2k
- フォーク
- 830
- 平均マージ
- 2日 12時間
- マージ済み PR（30日）
- 61
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
apache/devlake のほかの issue
-
type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 60/100
メンテナーはふだん 2 日以内に返信
-
type/bug
難易度 3/5 半日 初心者へのやさしさ 73/100
メンテナーはふだん 2 日以内に返信
-
[Bug][dora] calculateChangeLeadTime loads the whole commits_diffs deployment join into memory対応中かも @mdelacruz-avantio が 1 日前に担当しました。 オープン
難易度 3/5 1〜2日 初心者へのやさしさ 25/100
メンテナーはふだん 2 日以内に返信
-
[Refactor][Build] Build the core and all plugins into a single binary by default対応中かも @klesh が 1 日前に担当しました。 オープンcomponent/plugins type/refactor
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
メンテナーはふだん 2 日以内に返信
似ている issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
slavakurilyak/awesome-ai-agents#888 ·
メンテナーはふだん 1 日以内に返信
-
enhancement nav-pilot
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
メンテナーはふだん 1 日以内に返信
-
kind/enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
メンテナーはふだん 1 日以内に返信
-
feat(gmail): make gmail get --format raw text output the exact message, like drafts get --format rawオープンclawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
openclaw/gogcli#1276 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Seed a JRNYAx price before the last close so asset-detail S1.3 doesn't fail from 08:00Z to the openオープンbug tests
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
lognorman20/monaco#7231 ·