Getting Started

• 1. Introduction
• 2. What's New
• 3. Scope
• 4.1 General setup
• 4.2 Labels
• 4.3 Project task templates and checklists
• 4.4 Notifications

1. Introduction

Part of the Agile Project Management manual — see also 2. What's New, 3. Scope, 4.1 General setup, 4.2 Labels, 4.3 Project task templates and checklists, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

1.1 What Agile Project Management does

Agile Project Management (APM) adds an agile, drag-and-drop Kanban board to GLPI's own Project module. When creating a project you choose between a Standard GLPI Project (GLPI's normal project/task screens, untouched) or a Kanban Ticket project, which replaces the task and Kanban tabs with a single board mixing project tasks and linked tickets as cards, organised into columns that map onto project states.

1.2 Key benefits

• GLPI's native project Kanban shows only the project's tasks, so the tickets a team works on for the project never appear on the board, and it offers a limited set of features: no columns that follow the ticket workflow (new, assigned, planned, waiting, solved, closed), no labels, checklists or time tracking on the cards.
• Granting board access meant giving broad Project rights; there was no way to let someone move or comment on cards without also letting them edit fields, assign labels, manage a checklist, or reassign work independently of each other.
• GLPI's native global Kanban shows every project, but narrowing it down to the projects that matter means building complex search filters, and most changes to a card still mean leaving the board for the task or ticket form. The plugin's global board is filtered by project and label in a few clicks, and almost every action (moving, editing, assigning, commenting, linking tickets, checklists) is done without leaving the board.
• There was no lightweight way to tag or track sub-steps on a task — every distinction (urgent, in review, blocked on customer, three things left to finish before this is done) had to live in free-text description instead of something scannable at a glance.
• The board offered only one fixed layout — no way to separate tasks from tickets visually, no larger single-card view for a screen full of detail, and no way to focus the browser tab on just the board.

1.3 Features

1. Choose between a Standard GLPI Project and a Kanban Ticket project when creating a project.
2. Change a project's type later, one project at a time from its own tab or many at once with a massive action from the Projects list; switching back to Standard hides the board without deleting anything, and every change is recorded in the project's History.
3. View project tasks and tickets together on one board, colour-coded by card type: the project's own tickets always, and the tickets linked to its tasks on demand.
4. Map GLPI ticket statuses and project states onto board columns, configurable per installation.
5. Add, move, edit and delete cards, each gated by its own fine-grained right; a deleted task's card stays visible (greyed out) until restored or purged, rather than disappearing outright.
6. Link existing tickets to a project directly from the board, picking several at once from a list narrowed by free-text search, category, or "project-eligible" tickets (open tickets about the project's own items), so they appear as cards without leaving the Kanban view.
7. Comment on a card and attach files to it, kept as its own timeline separate from the card's fields.
8. Tag cards with custom, colour-coded labels, and filter the global board down to just the cards carrying a given label.
9. Give a project task its own checklist of sub-items, checked off individually and reordered as the work changes.
10. Group the board into swimlanes by item type, so tasks and tickets are visually separated instead of interleaved.
11. Switch a card's editor to a docked, single-panel view, or expand the whole board to fullscreen.
12. Filter the board down to just your own tasks, or just your groups' tasks, with one toggle each — on top of the general project/user/group/card-type filter below.
13. Filter the board by project, assigned user, group and card type at once, with the last filter combination remembered per user.
14. View every visible Kanban Ticket project on one aggregated global board, narrowed down to chosen projects or labels; the project picker itself can be searched and narrowed by project type, project state and finished projects.
15. Keep sort prefixes out of the board: a state named 1. To do so GLPI lists it in order shows as a plain To do column title, with the prefix pattern configurable.
16. Receive notifications on task creation, assignment, status change, percent-done change, comments, attachments and completion, each independently targetable at the task team, project managers, or both.
17. Track time on each task: the card shows its planned hours, the hours actually spent (on the task and on its linked tickets) and the hours left or over budget, in green or red.
18. Let the board fill in each task's real start and end dates as it moves from the first column to a finished state, with a separate right to correct them by hand.
19. Show only late tasks, those whose time spent is over their planned duration, with one toolbar toggle.
20. Link tickets to a task, or unlink them, from the task's own window, without leaving the board.
21. Keep the last few closed cards visible in the Closed column, the number being a Setup option, while older closed cards are only counted so large boards stay fast.
22. Click a person or group avatar on a card to show only their cards.
23. Add a card from a project task template with one click, its checklist copied to the new task.
24. Calculate a task's progress automatically from its solved tickets and done checklist items, switched on for the whole instance and overridden per project.
25. Switch the board to compact, two-line cards to see more of a busy board at once, remembered per user.
26. Show only the cards nobody is assigned to, with one toolbar toggle.
27. See how close each task is to its planned end, and which linked tickets are running late, from the colour of the card's date and tickets counter.
28. Open a card's GLPI history straight from the board, where every board action is recorded.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

2. What's New

Part of the Agile Project Management manual — see also 1. Introduction, 3. Scope, 4.1 General setup, 4.2 Labels, 4.3 Project task templates and checklists, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

Unreleased — 2.2.0, not yet published

New

• Time on each task: cards and the card window compare planned hours with the hours spent on the task and its tickets, in green while there is time left and red once over. See 5.3.4.1 Read the hours on a card.
• Real start and end dates, filled in by the board as a task moves, and correctable with the new Edit real dates right. See 5.3.4.3 How the board fills in the real dates.
• A Late toolbar toggle that keeps only the tasks over their planned hours. See 5.3.4.4 Show only late tasks.
• A Tickets section in the task's card window to see, link and unlink the task's tickets, with the new Link tickets to a task right. See 5.3.6 Tickets linked to a task.
• The Closed column keeps its most recently closed cards visible, set by the new Closed cards shown option; older ones are only counted, so large boards load faster. See 5.1.4.3 The Closed column and 4.1.2 Configuration.
• Click an avatar on a card to show only that person's or group's cards; a card shows at most three people or groups, with a "+N" for the rest. See 5.1.7.7 Show only one person's or group's cards.
• The followups in the card window can be hidden or shown, with a count on the button. See 5.2.3.1 Add a followup, or hide the followups.
• Long card titles fit on one line (hover to read them in full), and the Assign labels window shows labels as coloured chips, like the label filter.
• A ++ button next to each column's + adds a card from a project task template, checklist included. See 5.3.1.2 Add a card from a template.
• A task's progress can be calculated automatically from its solved tickets and ticked checklist items, switched on in the configuration and overridden per project. See 4.1.2 Configuration and 5.1.1.2 Change the type of one project.
• Compact cards: two-line cards with labels as thin strips, to see more of a busy board. See 5.1.8 Compact cards.
• An Unassigned toolbar filter keeps only the cards nobody is assigned to. See 5.1.7.3 Show only unassigned cards.
• A task's date turns green, amber, red or black as its planned end approaches or passes, and the tickets counter takes the worst Time to resolve colour of its tickets. See 5.3.3.4 Dates and their colour.
• The project title at the top of the project page shows the project's state, planned end, percent done, durations and variance. See 5.1.2.2 Read the project title.
• A Historical button in the card window opens the task or ticket's history, where every board action is now recorded. See 5.2.2.2 Buttons and counters in the window.
• A new Edit planned dates right controls who can change a task's planned dates. See 4.1.4 Permissions.
• The task window's Link tickets button opens the same window as the toolbar's, limited to that task's tickets. See 5.3.6.2 Link or unlink a ticket.
• Ticket cards show their Time to resolve alarm next to the priority, coloured by how close it is. See 5.4.1.3 Time to resolve alarm.
• Compact cards now show a task's linked-tickets counter and a time icon listing its durations, and a ticket's type icon and priority strip. See 5.1.8 Compact cards.
• A task's hours spent turn into a red badge once over its planned duration. See 5.3.4.1 Read the hours on a card.
• Project and task state lists, including the project filter's, show only their own states, without the sort prefix.
• The column for tasks without a state is now called No status; it has no add buttons and disappears once empty. See 5.1.4.1 Read a column header.

Fixed

• Unlinking a ticket from a card removes it from its task only, keeping it on the project, instead of failing; it needs the Link tickets to a task right, like the task's Tickets section.
• Updating the plugin grants its new rights to the profiles that can update projects, instead of leaving new features read-only.
• Fields you cannot edit in the card window are greyed out and locked.
• Collapsed columns stay collapsed after the board reloads, and show their card count under the column name.
• Card dates are shorter, so the card footer no longer overflows.
• On a project's own board, the project code shows once in the title instead of on every card.
• The project board loads for users working in a sub-entity with child entities included.
• Deleted tasks shown with Show deleted tasks no longer count in column totals or match filters, and can only be restored or purged.
• Cards you can't move can no longer be dragged, and a card dropped on the No status column is refused with a clear message.
• Pinning the card window no longer squeezes the board.
• Closing the toolbar's Link tickets window updates the board without reloading the page.

2.1.0 — 2026-09-22

New

• Coloured labels on cards, managed under Setup → Dropdowns → Kanban labels, with a label filter on the global board. See 5.5.1 Labels on task and ticket cards.
• Checklists on task cards, with a progress ring on the card, which task templates can pre-fill. See 5.3.5 Checklists on task cards and 4.3.1 Setting up project task templates and checklists.
• A project's type can be changed after creation, from its own tab or for several projects at once from the Projects list; switching back to Standard keeps the board, its order, checklists and labels. See 5.1.1 Choosing and changing a project type.
• A redesigned Link tickets window with search, a category filter and a project-eligible switch, whose defaults are set in the configuration. See 5.1.7.11 Link tickets to a project.
• The board can be grouped into Project tasks and Tickets rows. See 5.1.7.6 Group by item type.
• A single Filter projects window on the global board, searchable and narrowed by type, state and finished projects. See 5.1.7.9 Filter by project.
• Deleted tasks can be shown, restored or permanently deleted from the board. See 5.3.7 Deleted task cards.
• Column titles and the state filter show state names without their sort prefix, set in the configuration. See 4.1.2 Configuration.

Fixed

• Kanban notifications reach the task team and the project managers.
• Applying the project or label filter no longer reloads the page.
• Light label colours stay readable, with dark or light text chosen automatically.
• The board no longer shows tickets a user has no right to read, and card actions respect the user's entities and rights.
• Many smaller display and permission fixes on the board and in the card window.

2.0.0 — 2026-08-11

New

• GLPI 11 compatibility.

Fixed

• Nothing reported for this release.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

3. Scope

Part of the Agile Project Management manual — see also 1. Introduction, 2. What's New, 4.1 General setup, 4.2 Labels, 4.3 Project task templates and checklists, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

Reference only — see 4. Setup for how to configure each of these.

3.1 Assets, management & administration items

• Projects — gain a Type (Standard GLPI Project or Kanban Ticket), set on the project's Agile Project Management tab. A Kanban Ticket project gets a Kanban board tab, which replaces GLPI's own Kanban and Project tasks tabs.
• Project tasks — each task card is a project task: its name, description, assigned users and groups, dates, duration, type and state are those of the task itself, so a change on the board is a change to the task.
• Tickets — two kinds of ticket appear as cards. A ticket linked to the project itself always has a card. A ticket linked to one of the project's tasks is counted on the task's card and gets a card of its own, with a dashed border, only when Show tickets linked to a task is switched on. A ticket card's column follows the ticket's status; on the board it can only be moved to Pending, which puts the ticket on hold with a followup. Its other fields are changed in the ticket itself.
• Project states — used as the board's columns; adding, renaming or flagging a state as finished changes what the board shows.
• Project task templates — gain a Checklist tab, whose items are copied to a task created from the template.
• Profiles — gain an Agile Project Management rights tab (see Permissions below).

3.2 Automatic actions

None.

See 4.1.2 Configuration.

3.3 Notifications

The plugin adds seven notifications, created active on install. They are ordinary GLPI notifications, listed under Setup → Notifications → Notifications with the item type Kanban. They concern Kanban Ticket projects only: each is sent by an action on the plugin's board, so a standard project, a task changed in GLPI's own project task form, or a percent done set by automatic progress sends GLPI's usual notifications, never these.

Notification	Sent when
New Task	A task card is created.
New User in task	A user is assigned to a card.
Update Task Status	A card moves to another column.
Update Task Percent Done	A task's percent done changes.
New Comment	A comment is posted on a card.
New Attachment	A file is attached to a card.
Complete Task	A card reaches a finished column.

Besides GLPI's own recipients, each notification can be sent to the project task team (users or groups, including a group's managers only or everyone except them), the contacts and suppliers of the project team, and the project's manager (user or group, with the same manager splits). On install, every notification is sent only to the project's Manager; team members get nothing until a recipient such as Project task team user is added on the notification's Recipients tab.

3.4 Rules

None.

3.5 Permissions

Rights are set per profile under Administration → Profiles → a profile → Agile Project Management tab. The tab has four rows. Every box on it is listed below, exactly as labelled. None of the boxes implies another: ticking one does not tick any other.

Kanban row — what a user can do on a board (a project's Kanban tab and the global Kanban board):

• Add a card — create a new card (always a project task) from a column's menu or the Add a card button.
• Move a card — drag a task card to another column, which changes the task's state, or drag a ticket card to Pending to put the ticket on hold (the only move a ticket card allows).
• Edit title — change a card's title in the card window.
• Edit description — change a card's description in the card window.
• Delete a card — on a task card, deletes the task: it stays on the board greyed out and can be brought back. On a ticket card that is linked to a task, the Unlink button removes the ticket from that task only; the ticket stays linked to the project and its card stays on the board. Unlinking also needs Link tickets to a task and the right to update the project.
• Restore a card — bring a deleted task card back to normal.
• Permanently delete a card — remove a deleted task card for good. Not granted on install; give it deliberately, because it cannot be undone.
• Assign user to a card — add or remove the users assigned to a card.
• Assign a label to a card — put labels on a card or take them off (Assign labels in the card window). Creating and editing the labels themselves is the Kanban labels row below.
• Edit a card checklist — add, edit, reorder, tick or delete the checklist items of a task card. Without it the checklist is read-only.
• Add comment to a card — post a comment from the card window. For a ticket card, the comment becomes a followup on the ticket.
• Edit real dates — correct a task's Real start date and Real end date in the card window. Without it the board still fills them in as the task moves, but the two fields are read-only.
• Edit planned dates — change a task's Planned start date and Planned end date in the card window. Everyone who can see the card still sees them.
• Link tickets to a task — add tickets to a task, or remove them, from the Tickets section of the task's card window. Removing one only unlinks it from the task; the ticket stays linked to the project.

Kanban labels row — maintaining the label list under Setup → Dropdowns → Kanban labels:

• Read — see the label list and each label's details.
• Update — rename a label or change its colour, entity or comments.
• Create — add new labels.
• Purge — delete a label for good; it disappears from every card that carried it.

Checklist templates row — maintaining the checklist items of project task templates (Setup → Dropdowns → Project task templates → a template → Checklist tab):

• Read — see a template's checklist items.
• Update — edit an item's text.
• Create — add items.
• Purge — delete items.

Project type row:

• Change type — shows the plugin's tab on a project, where its type is changed, and the Change project type action of the Projects list. Without it, a project keeps the type chosen when it was created. The user also needs the right to update that project.

On a fresh install, every box above is ticked except Permanently delete a card, and only on profiles that can already update projects. When the plugin is updated, rights added in the new version (such as Edit real dates, Edit planned dates and Link tickets to a task) are granted once to those same profiles, so nobody loses access to a new feature; unticking one afterwards is kept.

GLPI core rights still apply on top: seeing a ticket card's private comments needs GLPI's own See private ones right for followups (on the profile's Assistance tab), which is not part of this tab, and a user only sees the projects and tickets GLPI already lets them see.

See 4.1.4 Permissions.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

4.1 General setup

Part of the Agile Project Management manual — see also 1. Introduction, 2. What's New, 3. Scope, 4.2 Labels, 4.3 Project task templates and checklists, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

4.1.1 Installation

Copy the plugin folder into GLPI's plugins/ directory, then install and activate it from Setup → Plugins. Installing creates the configuration with sensible defaults, grants the Kanban rights (every one except Permanently delete a card), the label rights and the checklist template rights to the profiles that can already update projects, and registers the notification events described below.

4.1.2 Configuration

Open Setup → General and choose the Agile Project Management tab. This is one global configuration for the whole GLPI instance: it does not change per entity or per project. The screen has three blocks. For each option below: what it does, where you see the effect, and an example of when it helps.

General options

• Task background — the background colour of every task card.
  • Where: the card front on a project's Kanban tab and on the global Kanban board (main menu), and the outline of the placeholder shown while a task card is being dragged.
  • Example: set it to a pale green so task cards stand apart from tickets on a busy board.
• Ticket background — the background colour of every ticket card.
  • Where: the same two boards.
  • Example: a pale orange makes customer tickets stand out from internal task work at a glance.
• Request sources by default — the request source written on the followups the board adds to a ticket on your behalf. Empty means GLPI's own default request source.
  • Where: a comment posted on a ticket card from the card window, and the followup created by the Set the status to pending dialog when a ticket card is moved to the Pending column. The value shows in that followup's details in the ticket timeline.
  • Example: choose a request source called Kanban, so a supervisor reading a ticket can tell which followups came from the board rather than from a phone call or an e-mail.
• Default ticket category filter — the category already selected in the Category filter when the Link tickets dialog opens.
  • Where: board toolbar → Link tickets button → the dialog's Category filter. The user can change or clear it every time.
  • Example: a hardware team that almost always links Hardware > Printers tickets set it to that category, so the list opens already narrowed to the tickets they want.
• Closed cards shown — how many of the most recently closed cards the Closed column keeps visible, from 0 to 50; default 3. Older closed cards are not loaded, only counted in the column header, which keeps a board with a long history fast. At 0 the column shows only its count.
  • Where: the Closed column of every board, whose note reads "Showing the last 3" while more cards are closed than shown. On the global board the number applies to the whole column, not to each project.
  • Example: a team that often reopens a task it closed that morning raises it to 10, so the task is still on the board to drag back.
• Project-eligible tickets by default — whether the Project-eligible tickets switch in the Link tickets dialog starts switched on. That switch lists only open tickets (neither solved nor closed), not yet linked to this project, that concern one of the items (computers, printers, software…) attached to the project.
  • Where: board toolbar → Link tickets → Project-eligible tickets switch. The user can switch it off or on every time.
  • Example: in an instance with thousands of tickets, a project that replaces the printers of one office lists that office's printers as its items; with this on, the dialog opens showing only the open tickets about those printers.

State labels

Teams often put a sort prefix in state names so GLPI lists them in a useful order, such as A. Open, B. In progress for project states and 1. To do, 2. Doing for task states. This block keeps those prefixes off the board.

• Strip sort prefix from state labels — the master switch for the two patterns below. Off, both patterns are ignored and states appear exactly as named.
  • Where: board column titles and the global board's project picker (see below).
  • Example: switch it off while testing new state names, to see the raw names on the board.
• Task state prefix regex — the pattern removed from the start of a state name when it is shown as a column title. The default /^\d+[-.]\s*/ removes a number followed by a dot or a dash and any spaces. If removing it would leave nothing, the full name is kept.
  • Where: the column titles on every board.
  • Example: the state 1. To do appears as the column To do, while GLPI's own state lists keep the order 1, 2, 3.
• Project state prefix regex — the pattern that marks a state as a project state rather than a task state. The default /^[A-Za-z][-.]\s*/ matches one letter followed by a dot or a dash, as in A. Open.
  • Where: global Kanban board → Filter projects → the Project state drop-down, which only offers the states matching this pattern.
  • Example: when project and task states share GLPI's single state list, this keeps task states such as 2. Doing out of the project picker, so filtering projects by state only shows states a project can actually be in.

Both patterns are full PHP regular expressions, including the /.../ delimiters. An invalid pattern is refused on save with an error message, and the previous value is kept.

Kanban Ticket

• New, Processing (assigned), Processing (planned), Pending, Solved, Closed — each picks the project state behind that column. A ticket card sits in the column of its ticket's status, and moves on its own when that status changes in the ticket. Task cards can be dragged to any column; ticket cards only to Pending. Only states chosen here become columns, always in this order. A card whose state is not mapped to any column is not lost: it goes to an extra No status column at the far left, which only appears while at least one card needs it. The No status column has no add buttons and refuses dropped cards.
  • Where: the columns of every Kanban Ticket board, and which column each ticket card appears in.
  • Example: map Pending to your Waiting for customer state: dragging a ticket card there puts the ticket on hold and opens the Set the status to pending dialog for the followup and the pending reason.
• Hide native project tasks tabs on Kanban Tickets — on by default. Removes two of GLPI's own tabs from a Kanban Ticket project: GLPI's native Kanban tab and the Project tasks tab, so the plugin's board is the only place tasks are managed.
  • Where: the tab list of a Kanban Ticket project (Tools → Projects → a project).
  • Example: leave it on so the team is not tempted to edit tasks in two places; switch it off if someone still needs GLPI's task list, for example to export it.
• Calculate task progress from tickets and checklist — sets a task's percent done from its linked tickets and its checklist: the share of them that is done, where a ticket counts once it is solved or closed and a checklist item once it is ticked. It is updated whenever a ticket or an item changes, even by a user who cannot edit the task. A task with neither tickets nor a checklist keeps the percent typed by hand. This is the default for every project; each project can keep it, or switch it on or off for itself, on its Agile Project Management tab.
  • Where: the progress bar of task cards, and the task's Percent done.
  • Example: switch it on so a task with three tickets shows 67% as soon as two of them are solved, without anyone updating the task.

Kanban labels

Labels are managed under Setup → Dropdowns → Kanban labels (listed under the plugin's name). Each label has:

• Name — the text on the chip. Example: Urgent, Waiting for supplier.
• Color — the chip background. The chip text switches between black and white automatically, whichever reads better on the colour chosen. Default grey. Example: red for Urgent, so it catches the eye among other labels.
• Entity and Child entities — where the label can be used. A label belongs to an entity, not to one project, so it is shared by every project of that entity, and of its sub-entities when Child entities is on. Example: create Urgent once in the root entity with Child entities on, and every team can use it and filter the global board by it.
• Comments — notes for administrators; not shown on the board.

Where labels appear: as chips on the card front and in the card window (Assign labels), and in the global board's Filter by label dialog. Purging a label removes it from every card that carried it.

4.1.3 The configuration screen

The configuration is one screen with three blocks. The screenshots below show each block with its default values; what every option does is explained in 4.1.2 Configuration.

4.1.3.1 General options

Open Setup → General and choose the Agile Project Management tab. The first block sets the two card colours, the request source used for followups the board writes, and the two defaults of the Link tickets dialog. Here the dialog opens already filtered on the Bug report category.

4.1.3.2 State labels

The second block controls how sort prefixes are removed from state names on the board. With the defaults shown, the task state 1. To do becomes the column To do, and states starting with a letter, such as A. Open, are the ones offered as project states in the global board's Filter projects window.

4.1.3.3 Kanban Ticket

The third block decides the board's columns. Each of the six ticket statuses (New, Processing (assigned), Processing (planned), Pending, Solved, Closed) picks the project state that becomes its column, always in that order; a state not picked here is not a column, and its cards go to No status. A ticket card sits in the column of its ticket's status. The block also holds Hide native project tasks tabs on Kanban Tickets and Calculate task progress from tickets and checklist; every option is described in 4.1.2 Configuration. In this example Pending maps to 4. Waiting for customer, so dragging a ticket card into that column puts the ticket on hold. Click Save at the bottom of the screen to apply any change.

4.1.4 Permissions

Rights are set per profile under Administration → Profiles → a profile → Agile Project Management tab. The tab has four rows. Every box on it is listed below, exactly as labelled. None of the boxes implies another: ticking one does not tick any other.

Kanban row — what a user can do on a board (a project's Kanban tab and the global Kanban board):

• Add a card — create a new card (always a project task) from a column's menu or the Add a card button.
• Move a card — drag a task card to another column, which changes the task's state, or drag a ticket card to Pending to put the ticket on hold (the only move a ticket card allows).
• Edit title — change a card's title in the card window.
• Edit description — change a card's description in the card window.
• Delete a card — on a task card, deletes the task: it stays on the board greyed out and can be brought back. On a ticket card that is linked to a task, the Unlink button removes the ticket from that task only; the ticket stays linked to the project and its card stays on the board. Unlinking also needs Link tickets to a task and the right to update the project.
• Restore a card — bring a deleted task card back to normal.
• Permanently delete a card — remove a deleted task card for good. Not granted on install; give it deliberately, because it cannot be undone.
• Assign user to a card — add or remove the users assigned to a card.
• Assign a label to a card — put labels on a card or take them off (Assign labels in the card window). Creating and editing the labels themselves is the Kanban labels row below.
• Edit a card checklist — add, edit, reorder, tick or delete the checklist items of a task card. Without it the checklist is read-only.
• Add comment to a card — post a comment from the card window. For a ticket card, the comment becomes a followup on the ticket.
• Edit real dates — correct a task's Real start date and Real end date in the card window. Without it the board still fills them in as the task moves, but the two fields are read-only.
• Edit planned dates — change a task's Planned start date and Planned end date in the card window. Everyone who can see the card still sees them.
• Link tickets to a task — add tickets to a task, or remove them, from the Tickets section of the task's card window. Removing one only unlinks it from the task; the ticket stays linked to the project.

Kanban labels row — maintaining the label list under Setup → Dropdowns → Kanban labels:

• Read — see the label list and each label's details.
• Update — rename a label or change its colour, entity or comments.
• Create — add new labels.
• Purge — delete a label for good; it disappears from every card that carried it.

Checklist templates row — maintaining the checklist items of project task templates (Setup → Dropdowns → Project task templates → a template → Checklist tab):

• Read — see a template's checklist items.
• Update — edit an item's text.
• Create — add items.
• Purge — delete items.

Project type row:

• Change type — shows the plugin's tab on a project, where its type is changed, and the Change project type action of the Projects list. Without it, a project keeps the type chosen when it was created. The user also needs the right to update that project.

On a fresh install, every box above is ticked except Permanently delete a card, and only on profiles that can already update projects. When the plugin is updated, rights added in the new version (such as Edit real dates, Edit planned dates and Link tickets to a task) are granted once to those same profiles, so nobody loses access to a new feature; unticking one afterwards is kept.

GLPI core rights still apply on top: seeing a ticket card's private comments needs GLPI's own See private ones right for followups (on the profile's Assistance tab), which is not part of this tab, and a user only sees the projects and tickets GLPI already lets them see.

4.1.5 The profile rights tab

The plugin's rights sit on their own tab of every GLPI profile. What each box allows is listed in 4.1.4 Permissions.

4.1.5.1 Open the Agile Project Management tab on a profile

Go to Administration → Profiles, open a profile, then its Agile Project Management tab. Tick or untick the boxes and click Save. The screenshot shows the Super-Admin profile of the demo instance.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

4.2 Labels

Part of the Agile Project Management manual — see also 1. Introduction, 2. What's New, 3. Scope, 4.1 General setup, 4.3 Project task templates and checklists, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

4.2.1 Setting up labels

Labels are prepared by an administrator before the team uses them on the board.

4.2.1.1 The label list

Go to Setup → Dropdowns and choose Kanban labels, listed under the plugin's name. The list shows every label with its colour.

4.2.1.2 Create or edit a label

Click Add, or open a label, to set its Name, Color, Entity and Child entities. The fields are described in 4.1.2 Configuration, under Kanban labels.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

4.3 Project task templates and checklists

Part of the Agile Project Management manual — see also 1. Introduction, 2. What's New, 3. Scope, 4.1 General setup, 4.2 Labels, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

4.3.1 Setting up project task templates and checklists

A project task template can carry a checklist, so every task created from it on the board starts with the same items.

4.3.1.1 Add a checklist to a task template

Go to Setup → Dropdowns → Project task templates, open a template and choose its Checklist tab. Add the items the task should always start with. A task created on the board from this template (Create from a template) gets these items as its checklist. Maintaining these items needs the Checklist templates rights on the profile.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.

4.4 Notifications

Part of the Agile Project Management manual — see also 1. Introduction, 2. What's New, 3. Scope, 4.1 General setup, 4.2 Labels, 4.3 Project task templates and checklists, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

4.4.1 Configuring Kanban notifications

The plugin's notifications are ordinary GLPI notifications, created active when the plugin is installed. They concern Kanban Ticket projects only: every event is sent by an action on the plugin's board (a project's Kanban tab or the global Kanban board), and only Kanban Ticket projects have one. Standard projects, and changes made to a task in GLPI's own project task form, send GLPI's usual project task notifications instead, never these. A percent done changed by automatic progress sends nothing either. The recipients they offer are listed in 3.3 Notifications.

4.4.1.1 Find the plugin's notifications

Go to Setup → Notifications → Notifications and search on the item type Kanban. The seven events of the plugin are listed; each can be edited, switched off or given other recipients like any GLPI notification:

• New Task: a task card is added to the board.
• New User in task: a user is assigned to a card.
• Update Task Status: a task card is moved to another column.
• Update Task Percent Done: a task's percent done is changed in its card window.
• New Comment: a comment is posted from a card window.
• New Attachment: a file is attached from a card window.
• Complete Task: a task card is moved to a column whose state is flagged Finished; the task is set to 100% and Update Task Status is sent too.

4.4.1.2 Choose who is notified

Open a notification and choose its Recipients tab. Besides GLPI's own recipients, the list offers the project task team, the project team's groups, contacts and suppliers, and the project manager. On install, every event notifies only the Manager.

Generated for Agile Project Management 2.2.0-beta.2 on GLPI 11.0 — 2026-09-27.