Agile Project Management

• 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
• Using Agile Project Management
• 5.1 The board
• 5.2 Working with cards
• 5.3 Project task cards
• 5.4 Ticket cards
• 5.5 Labels
• 6. Troubleshooting

Getting Started

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.

Using Agile Project Management

5.1 The board

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, 4.4 Notifications, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

5.1.1 Choosing and changing a project type

Every project is either a Standard GLPI Project, with GLPI's own project and task screens unchanged, or a Kanban Ticket project, managed from the plugin's board mixing project tasks and linked tickets. The type is chosen when the project is created and can be changed later by a user with the Change type right.

5.1.1.1 Pick the type of a new project

Choose Tools → Projects and click Add. Before the usual project form, the plugin asks which type of project to create. Kanban Ticket opens the project form; once saved, the project opens on its Kanban tab.

5.1.1.2 Change the type of one project

Open the project and choose its Agile Project Management tab. Pick the other Type and click Save. Nothing is deleted: a Kanban Ticket project turned back into a standard project keeps its board data, and returns to it if switched back. The change is written to the project's Historical tab.

The same tab has Calculate task progress from tickets and checklist, which overrides the global option of the same name for this project: keep the global setting, or switch automatic progress on or off for this project only. The global value is shown next to the field while it is inherited.

5.1.1.3 Change the type of several projects at once

In Tools → Projects, tick the projects, click Actions and choose Change project type. Pick the new type and click Post. Every project changed is logged in its own Historical tab.

5.1.2 The Kanban board

A Kanban Ticket project shows its work as a board instead of the standard project task list. Each column is a project state, and each card is either a project task or a ticket linked to the project. The two are given different background colours, so which kind of work a card represents is obvious without reading it.

5.1.2.1 Open the board

Open the project and choose its Kanban tab. The board replaces the usual task list and fills the width of the page.

A Kanban Ticket project, one column per project state

5.1.2.2 Read the project title

At the top of the project page, the title label shows the project's code and state; hover it for the project's full name. After them come its key figures, with the same icons and colours as the task cards:

• Planned end date of the project.
• Percent done.
• Planned duration and effective duration (the time actually spent).
• Variance: planned minus effective, in hours and as a percentage; positive and green while there is time left, negative and red once over budget.

Hover a figure for its name. On a narrow screen some figures are hidden to make room. The label takes the main menu's colours from the active GLPI theme.

5.1.2.3 Columns are project states

Each column is a project state, chosen in the configuration for one of the six ticket statuses, so the board always reads from new work on the left to closed work on the right. A column title is the state's name without its sort prefix, so a state named 1. To do shows as To do. The number beside a column name is how many cards it currently holds, which is the quickest way to spot work piling up in one place. In this example the columns are To do, In progress, Scheduled, Waiting for customer, Solved and Closed.

A column, its name and its card count

5.1.2.4 Read a card at a glance

Without opening anything, a card tells you: its title, the project code it belongs to, its type, who it is assigned to, how far along it is, its planned and spent hours, its dates, and whether it carries labels, a checklist, comments or attachments. Every icon on it is explained in Icon meanings and tooltips, and the hours in Time on a task.

One card, carrying labels, assignees, a comment and linked tickets

5.1.2.5 Open a card

Click a card to open it. Everything about that task or ticket is edited here rather than on the board itself — see The card window.

Note: Task cards and ticket cards are given the two background colours set in Setup, so the two kinds of work stay distinguishable even on a full board.

Note: The board only lists projects that are not templates, not deleted, and whose state is not flagged "finished" in Setup > Assistance > Project states — a project can stop appearing here simply because its state changed to a finished one.

5.1.3 The global Kanban view

Instead of opening one project at a time, Kanban in the main menu shows every Kanban Ticket project the user can see on a single aggregated board, with each card labelled with its project name and code.

5.1.3.1 Open the global Kanban view

Choose Kanban from the main menu. The same filters, card actions and drag-and-drop behaviour apply here as on a single project's board — the only difference is that cards from every visible Kanban project are mixed together.

Note: The global board only shows the projects and tickets GLPI already lets you see; it adds no visibility of its own.

Note: Each card displays its project name and code alongside its title, so you can tell which project a task or ticket belongs to at a glance.

5.1.4 Columns and collapsing them

Columns are project states. They are not created, moved or deleted on the board: an administrator chooses them in the configuration (see Configuration, Kanban Ticket block), and the board shows them in that order.

5.1.4.1 Read a column header

Each column header shows the state name, without its sort prefix, and the number of cards in the column. A card with no state, or with a state not mapped to any column, goes to an extra No status column at the far left. It is shown only while it has cards and disappears as soon as the last one is moved out. It has no add buttons: a new card always starts in a column with a project state. A collapsed column shows its card count under its name, and stays collapsed when the board reloads.

5.1.4.2 Collapse a column

Click the left-pointing arrow icon at the left of a column header to collapse it, hiding its cards but keeping the column label visible vertically. Click the right-pointing arrow to expand it again.

The first column collapsed to a narrow strip

5.1.4.3 The Closed column

The Closed column shows only its most recently closed cards (3 by default, set by Closed cards shown in the configuration) and a "Showing the last 3" note while more are closed; its header counts them all. Older closed cards are not loaded, which keeps a board with a long history fast; they remain in GLPI's own project and ticket lists. Dropping a card into Closed still works: it becomes the newest shown card.

On the global board, the Closed column keeps its last 3 cards and counts the rest

5.1.5 Filtering the board and saving a personal filter

The board can be filtered by project, assigned user, group and card type. A filter is saved per user, not per project — it is remembered the next time you open any Kanban board.

5.1.5.1 Open the filter panel

Click the search icon in the toolbar above the board. The filter inputs appear: project, user, group and card type. Combining several narrows the board to cards matching all of them.

5.1.5.2 Save the filter

Once a combination is useful, it is saved automatically for that user and reapplied on the next visit — there is one saved filter per user, replaced each time a new combination is applied.

5.1.6 Moving a card between columns

Task cards and ticket cards move differently. A task card can be dragged to any column, which changes the task's project state. A ticket card's column follows the ticket's own status, through the status mapping of the configuration; on the board it can only be put on hold.

5.1.6.1 Drag a card to another column

Drag a task card from its current column and drop it onto another. The task's state changes immediately, its real dates are filled in as described in Time on a task, and the Update Task Status notification is sent.

A ticket card can only be dragged to the Pending column: the Set the status to pending window opens for the followup and the pending reason, and the ticket is put on hold. Dropping a ticket anywhere else is refused with a message. Other status changes (assigning, solving, closing) are made in the ticket itself, and its card then moves to the matching column on its own.

Note: Moving a card requires the Move a card right; without it the card cannot be dragged at all (see Permissions in Setup). A card can't be dropped on the No status column: the board refuses it with a message asking for a column with a project state.

5.1.7 Board toggles, menus and view options

The toolbar above the board offers several toggles and dropdowns to control what you see and how the board behaves. Its buttons are grouped by purpose: project and label filters, user filters, quick filters, actions, then view options. Hover any button for its name.

5.1.7.1 Show only my tasks

Click the checkbox icon to filter the board to show only cards assigned to you. Click again to show all cards.

With the toggle on, the board keeps only the cards assigned to you

5.1.7.2 Show only my groups' tasks

Click the users icon to filter the board to show only cards assigned to groups you belong to.

5.1.7.3 Show only unassigned cards

Click Unassigned to keep only the cards with no user assigned, for example to pick up work nobody owns yet. It can be combined with My tasks and My groups tasks.

5.1.7.4 Show tickets linked to a task

A project has two kinds of ticket cards. A ticket linked to the project itself always has its own card. A ticket linked to one of the project's tasks is counted on that task's card (the ticket ring) and, by default, has no card of its own. Click the Show tickets linked to a task icon to show those tickets as cards too: they have a dashed border in the task colour, and an icon next to their date names the task. Click it again to hide them.

Tickets linked to a task, shown as cards with a dashed border

5.1.7.5 Show deleted tasks

Click the trash icon to display deleted task cards on the board (grayed out, marked as deleted). Deleted cards can be restored or purged via their detail panel.

5.1.7.6 Group by item type

Click the rows icon to organize the board into swimlanes — one for project tasks, one for tickets. Cards stay in their columns but are grouped by type for easier scanning.

5.1.7.7 Show only one person's or group's cards

Click an avatar on a card to keep only the cards of that user or group. A chip with the name appears in the toolbar; click its cross, or the same avatar again, to show every card. This replaces My tasks and My groups tasks while it is on.

The board filtered on one group; the chip in the toolbar resets it

5.1.7.8 Show only a card type

Use the Show dropdown, after the filter icon, to show all cards, only project tasks, or only tickets.

5.1.7.9 Filter by project (global Kanban only)

On the global Kanban, click the filter icon (Filter projects) to choose which projects the board shows. Search by name, narrow the list by Project type and Project state (which lists only project states, without their sort prefix), switch on Show finished projects to include finished ones, and tick the projects to keep (Select all shown / Clear), then click Apply. The badge on the icon shows how many projects are selected. Closing the window applies the choice without reloading the page, and it is saved for your next visit.

5.1.7.10 Filter by label (global Kanban only)

On the global Kanban, click the tag icon (Filter by label) to show only the cards carrying the ticked labels. No label keeps the cards that have none. See 5.5.3 Filtering the board by labels.

5.1.7.11 Link tickets to a project

Click Link tickets to open a window where you can search for existing tickets and link them to this project. It works like the Filter projects window: search, then tick tickets one by one or use Select all shown and Clear. The label filter and a task's own Link tickets window work the same way. Closing the window updates the board in place, without reloading the page.

5.1.7.12 Expand to fullscreen

Click the expand icon to hide GLPI's sidebar and header, giving the board the entire window. Click again to restore them.

5.1.7.13 Switch to docked editing

Click the pin icon to open cards for editing in a docked sidebar on the right instead of a modal popup. The docked editor overlaps the right side of the board; the columns narrow by at most a quarter to make room, so the board stays usable. Click again to switch back to modal editing.

5.1.8 Compact cards

Compact cards fit more of a busy board on the screen, showing each card on two lines.

5.1.8.1 Switch to compact cards

Click Compact cards in the toolbar's view options. Each card shrinks to two lines: the title, then the people and groups, dates and counters. Labels become thin coloured strips; hover one for its name. The second line shows as many people and groups as fit, then a +n whose tooltip names the rest. Compact cards keep the essentials:

• Task cards: the linked-tickets counter, and a time icon whose tooltip lists all the task's durations (planned, spent, left or over).
• Ticket cards: the Incident or Request icon, the priority as a coloured strip (hover it for its name), and the Time to resolve alarm when the ticket has one.

Click the button again for full cards.

The choice is remembered for you, separately for a project's board and the global board.

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

5.2 Working with cards

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, 4.4 Notifications, 5.1 The board, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

5.2.1 Task cards and ticket cards

The board shows two kinds of card. Task cards are the project's tasks and are edited on the board. Ticket cards are tickets linked to the project, or to one of its tasks, and are mostly edited in GLPI's own ticket form.

5.2.1.1 Task icon

A teal checklist icon in the card's top row marks the card as a project task, as opposed to a ticket. It is the same icon GLPI uses for project tasks elsewhere, so a card is identifiable as a task without reading anything else on it. Ticket cards show their own icon in this position instead — see the next step.

The teal task icon distinguishes a task card from a ticket card

5.2.1.2 Ticket type icon

A red exclamation circle (⚠) indicates an Incident ticket; a blue question mark (?) indicates a Request. These appear at the top of ticket cards.

Note: Task cards and ticket cards are colour-coded by background: the task background colour (configured in Setup > General options) for tasks, and the ticket background colour for tickets. This makes them easy to tell apart at a glance.

5.2.2 Card detail modal

Click any card to open its detail panel. In modal mode (the default), the panel is a popup window; in docked mode, it opens in a sidebar on the right. Either way, the form and available actions are the same.

5.2.2.1 Open a card

Click a card on the board. Its detail modal opens, showing the card's title, description, assigned user(s), dates, type, status, comments and attachments.

5.2.2.2 Buttons and counters in the window

The buttons at the top of the window show and hide its sections. The Followups, Checklist, Tickets and Labels icons carry a counter and share one colour code:

• Grey, no counter: the section is empty.
• Orange: the section has content but is hidden.
• Blue: the section is shown.

The Historical button opens the task or ticket in GLPI on its Historical tab, in a new browser tab. Every board action is recorded there, including checklist changes and team members added from the board; for a task, the effective duration shown is the one the board keeps. The button is shown only to users allowed to see the Historical tab.

5.2.2.3 Close the modal

Click Cancel at the bottom right of the modal (or the X button in the title bar) to close it without saving.

Note: Fields you can't edit are greyed out and locked, with a tooltip saying why. Modal editing is the default view. You can switch to docked editing (sidebar on the right) using the pin icon in the toolbar, which you may prefer for larger screens.

5.2.3 Followups

5.2.3.1 Add a followup, or hide the followups

The Followups section at the bottom of the card window lists the card's comments. Type a new one in the text box and click Send. For a ticket card it becomes a followup of the ticket. The followups button in the window's button bar shows how many there are and hides or shows the section, which keeps a long discussion out of the way while you edit the card; the choice is remembered. A new comment triggers the New Comment notification.

5.2.4 Saving card changes

5.2.4.1 Save changes

Click Save at the bottom right of the modal to save your changes and close the modal.

5.2.4.2 Discard changes

Click Cancel to close the modal without saving.

Note: The modal requires a title (name) for any new card. If you save without one, the form will highlight the missing field in red and prevent saving.

5.2.5 Icons shared by both kinds of card

These icons appear on task and ticket cards alike. Hover any of them for a tooltip.

5.2.5.1 Assigned user avatars

Small circular avatars along the bottom of the card show who the task is assigned to. A user with a profile picture is shown as that picture; a user without one is shown as their coloured initials, so people are still tellable apart. Avatars overlap to save space, and where more are assigned than fit, the last circle reads +N for the rest. Hover over any avatar for the full name.

Assigned users, shown as pictures or coloured initials

5.2.5.2 Assigned group avatars

A group assigned to the task appears in the same row as the users, as a purple circle with a group icon rather than a picture or initials — so a group is never mistaken for a person. Hover over it for the group name. Groups are assigned from the card's editor, not from the card face.

A group assigned to a task, alongside the assigned users

5.2.5.3 Comments icon

A comment bubble icon shows how many comments are on the card. Click it (if the modal is open) to scroll to the comments section.

5.2.5.4 Label chips

Colored chips on a card show labels assigned to it. Hover over a chip to see the full label name. If a card has many labels, extra ones collapse into a "+N" badge.

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

5.3 Project task cards

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, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.4 Ticket cards, 5.5 Labels, 6. Troubleshooting.

5.3.1 Adding a card

A new card is always a project task — ticket cards appear on the board once a ticket is linked to the project, they cannot be created directly from the board.

5.3.1.1 Add a card to a column

Click Add a card at the bottom of a column (or hover over the column header and select Add a card from the menu), give it a title, then fill in the detail panel that opens: description, assigned user(s) or group, start and end dates, planned duration, and type. The card is created directly in that column's project state.

5.3.1.2 Add a card from a template

Next to each column's + is a ++ button (Add a card from template). Click it, choose a Project task template and click Add. The number after a template's name is the size of its checklist.

5.3.1.3 Review the card filled from the template

The new card opens filled in from the template: name, description, type, planned duration, dates and percent done. Everything stays editable. The template's checklist is copied to the task when you click Save.

Note: Adding a card requires the Add a card right. Neither button is shown in a column for a finished state, or when no project task template exists (for ++).

5.3.2 Editing a task card

The detail modal for a task card contains several fields for entering and editing information.

5.3.2.1 Open a task card

Task cards are fully editable — you can change the title, description, assigned users, dates, duration, type and all other fields (depending on your permissions). Edit any field by clicking on it and making your changes.

5.3.2.2 Edit the title

Open the card and click on the Name field to edit it. A red asterisk marks required fields.

5.3.2.3 Edit the description

Click the Description field to edit the card's description. Each is a separate right (Edit title, Edit description), so a profile can allow one without the other.

5.3.2.4 Assign a user

Use the User field in the card detail panel to add or remove team members. This is gated by the Assign user to a card right.

5.3.2.5 Set start and end dates

Use the Planned start date and Planned end date fields to set the card's timeline. Everyone can see them; changing them needs the Edit planned dates right.

5.3.2.6 Set planned duration

Use the Planned duration dropdown to estimate how long the task will take.

5.3.2.7 Set the card type

Use the Type dropdown to categorize the task (e.g., Bug, Feature, Documentation). Available types are configured in Setup.

5.3.2.8 Attach a file

In the Files section of the modal, click the upload area or drag and drop a file to attach it to the card. Files attached to a card trigger the New Attachment notification and become regular GLPI documents linked to the underlying project task.

Note: Editing permissions are granular — each field is gated by its own right. A read-only field is grayed out and cannot be edited.

5.3.3 Reading a task card

A task card shows the task's type, time, dates, progress, checklist and linked tickets at a glance. Hover any icon for a tooltip.

5.3.3.1 Task card layout

A project task card shows:

• The card's title (the task name)
• Assigned user avatars (overlapping icons at the bottom)
• Type badge showing the task type (Development, Support, New Feature, Spike)
• Duration icon and duration estimate
• Creation date with date icon
• Progress bar showing percent done
• Comment and attachment counts at the bottom

5.3.3.2 Task type icon

A tag icon and label show the task's Type, one of the project task types defined under Setup → Dropdowns → Project task types, and set in the task's Type field. A task with no type shows neither the tag nor the planned duration next to it. Hover the tag to see the full type name when it is shortened. Ticket cards show their ticket type (Incident or Request) as an icon instead. In this example the types are Development, Support, New Feature and Spike.

5.3.3.3 Planned duration

A task's planned duration is the first figure of the card's time row, after a clock icon; the hours spent and the variance follow it, in hours and as a percentage, green while there is time left and red once over (see Time on a task). A task with no planned duration shows only the hours spent.

5.3.3.4 Dates and their colour

A calendar icon shows the task's planned dates, in days only; a range within one month shows the month once. Hover it for the full dates. Without planned dates the card shows its creation date.

The date's colour tells how close the task is to its planned end, using the same colours and thresholds as a ticket's Time to resolve:

• Grey: no planned end, or the task hasn't started and its planned start is still ahead.
• Green: on time; or finished on or before its planned end.
• Amber: the planned end is approaching.
• Red: the planned end is close (critical).
• Black: overdue; past its planned end, or finished after it.

5.3.3.5 Progress bar

A coloured bar shows how much of the task is complete (percent done, 0–100%). When a task is 100% complete, the bar turns green and the percentage is hidden. Percent done is either typed in the task, or calculated automatically from the task's solved or closed tickets and its done checklist items, when Calculate task progress from tickets and checklist is on (see 4.1.2 Configuration).

5.3.3.6 Attachments icon

A paperclip icon shows how many files are attached to the card. Click it (if the modal is open) to jump to the attachments section.

5.3.3.7 Checklist icon

A checkmark icon indicates the card has a checklist. Click it (if the modal is open) to show/hide the checklist panel.

5.3.3.8 Linked tickets ring

A task card with tickets linked to it shows a ring with a ticket icon and a count such as 1/3: tickets solved or closed, out of all the tickets linked to the task. The ring fills as tickets are solved and turns green when all are. Until then it takes the worst Time to resolve colour of its tickets, so a late ticket shows on the task too. Hover it for the details; the tickets themselves are listed in the task's card window (see Tickets linked to a task).

5.3.4 Time on a task: hours, real dates and late tasks

Each task card compares the time planned for the task with the time actually spent on it, and the board records when work on the task really started and ended. Both are kept up to date from the board itself, so the team does not have to fill them in.

5.3.4.1 Read the hours on a card

A task card with a planned duration shows three figures in its time row:

• Planned (clock) — the task's Planned duration.
• Spent (clock with a play sign, or a stop sign once the task is finished) — the task's Effective duration plus the time logged on the tickets linked to it. Hover it to see the breakdown. Once it goes over the planned duration it turns into a red badge, so an over-budget task stands out on the board.
• Left or over (delta) — planned minus spent, as a percentage of the plan. Green is time left; red, with a minus sign, is time over the plan.

A task with no planned duration shows only the hours spent.

A task over its plan: 24 h planned, 26 h spent, 8 % over

5.3.4.2 Hours and real dates in the card window

The card window repeats the planned and spent hours next to the task number, with the time left or over in hours and percent, and shows the time fields in its side panel:

• Real start date and Real end date — when work on the task really started and ended (see the next step).
• Effective duration (h) — the time spent on the task itself.
• Tickets duration (h) — the time logged on the tickets linked to the task, read-only here because it comes from the tickets.

5.3.4.3 How the board fills in the real dates

Moving a task on the board fills in its real dates:

• Leaving the first column (or the No status column) sets the Real start date, if it is still empty.
• Reaching a column whose project state is flagged Finished sets the Real end date (and the start date, if the task skipped straight there).
• Moving a task back out of a finished column clears its end date and keeps its start date.

A user with the Edit real dates right can correct either date by hand in the card window; for everyone else the two fields are read-only.

5.3.4.4 Show only late tasks

Click the Late icon (a clock with an exclamation mark) in the toolbar to keep only the tasks whose time spent is over their planned duration. Click it again to show every card.

With Late on, only the two tasks over their planned hours remain

5.3.5 Checklists on task cards

Project task cards can have a checklist — a list of subtasks that you can check off as you complete them. Checklists are task-specific: ticket cards do not have one.

5.3.5.1 Show/hide the checklist

Open a task card. If it has a checklist, a checkmark icon appears in the action bar at the top. Click it to toggle the checklist panel visible/hidden. The checklist appears below the description in the modal.

5.3.5.2 Check off a checklist item

In the checklist panel, click the checkbox next to an item to mark it complete. Completed items get a strikethrough and are slightly grayed out.

5.3.5.3 Add a checklist item

At the bottom of the checklist, type a new item name in the Add an item text box and click Add, or press Enter. The new item appears in the list, unchecked.

5.3.5.4 Edit a checklist item

Hover over a checklist item and click its text to edit it in place, then press Enter to save the change.

5.3.5.5 Delete a checklist item

Hover over a checklist item and an X icon appears on the right. Click it to remove the item from the checklist.

Note: Checklist permissions follow the card edit permissions — if you can edit the task, you can edit its checklist.

Note: A checklist progress ring appears on the card front (in the footer) showing the percentage of items checked. The ring fills as you complete items.

5.3.6 Tickets linked to a task

A task can have tickets linked to it, for example the incidents a fix is meant to solve. The task's card window lists them and lets you link or unlink tickets without leaving the board. Time logged on these tickets counts in the task's hours spent.

5.3.6.1 See the tickets of a task

Open a task card. The Tickets section, under the checklist, lists each linked ticket with a ring showing its status, its number and title (a link to the ticket), its technician and the time logged on it. The ticket button in the window's button bar shows how many of the linked tickets are solved (here 1/2) and shows or hides the section.

5.3.6.2 Link or unlink a ticket

To link tickets, click Link tickets at the bottom of the section. It opens the same Link tickets window as the toolbar button (see 5.1.7.11 Link tickets to a project), with the same search, Select all shown and Clear, but showing only this task's board tickets. To unlink one, click the broken-link icon at the end of its row: the ticket is removed from the task only and stays linked to the project, so its own card stays on the board. Both need the Link tickets to a task right; without it the section is read-only.

5.3.7 Deleted task cards

When a task is deleted, its card remains on the board (grayed out) until it is purged. You can restore or purge deleted tasks.

5.3.7.1 Show deleted tasks

By default, deleted task cards are hidden. Click the trash icon in the toolbar to show them. Deleted cards appear faded with a "Deleted" label. They are not counted in the column totals, and no filter or search matches them. A deleted card can only be restored or purged, not edited or moved.

5.3.7.2 Restore a deleted task

Open a deleted task card and click Restore in the action bar. The task is restored and becomes fully editable again. You must have the Restore a card right.

5.3.7.3 Permanently delete (purge) a task

Open a deleted task card and click Purge in the action bar. The task is permanently deleted and cannot be restored. You must have the Permanently delete a card right.

Note: Restoring and purging require their own rights (Restore a card and Permanently delete a card). Without them, deleted cards cannot be acted on.

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

5.4 Ticket cards

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, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.5 Labels, 6. Troubleshooting.

5.4.1 Reading a ticket card

5.4.1.1 Ticket card layout

A ticket card has the ticket's own colour and shows, besides what a task card shows:

• The ticket number before the title (for example #15).
• The ticket type icon: a red exclamation circle for an Incident, a blue question mark for a Request.
• The priority, as a coloured badge.

A ticket linked to one of the project's tasks rather than to the project is shown differently; see Ticket linked to task indicator below.

5.4.1.2 Priority badge

Ticket cards show a colored priority badge (low, medium, high, very high). The color intensity increases with priority. Task cards do not show priority.

5.4.1.3 Time to resolve alarm

A ticket with a Time to resolve shows an alarm icon next to its priority, on full and compact cards alike. Hover it for the date. Its colour follows GLPI's own Time to resolve colours and thresholds, the same as a task card's date:

• Green: on time; or solved before its Time to resolve.
• Amber: the Time to resolve is approaching.
• Red: the Time to resolve is close (critical).
• Black: overdue; past its Time to resolve, or solved after it.

A ticket without a Time to resolve shows no alarm.

5.4.1.4 Ticket linked to task indicator

A ticket linked to a task of the project, rather than to the project itself, has no card of its own until Show tickets linked to a task is switched on in the toolbar. Its card then has a dashed border in the task colour, and a small icon next to its date; hover the icon to see which task it belongs to.

5.4.2 The ticket card window

5.4.2.1 Viewing a ticket card

Opening a ticket card shows its name, type, category, requester, watchers, assigned users and groups, and description, all read-only: these are changed in the ticket itself (the Open full form button opens it). From the board you can add a followup, private if you have the right, and assign labels. Files are attached in the ticket form. On the board a ticket card can only be moved to the Pending column (see Moving a card between columns); its other status changes come from the ticket.

5.4.2.2 Add a private comment

On a ticket card, tick the lock box next to the comment field before sending to make the followup private. It is then shown only to users with GLPI's See private ones right for followups. The box appears only for users who have that right.

5.4.2.3 Unlink a ticket from its task

When a ticket card is linked to a task, its window has an Unlink button. It removes the ticket from the task only: the ticket stays linked to the project, so its card stays on the board, and the ticket itself is untouched. It needs the Delete a card and Link tickets to a task rights and the right to update the project. The same can be done from the task's own window (see Tickets linked to a task).

Note: To edit a ticket's actual details (type, category, etc.), open its full form in GLPI. The detail modal has a button to open the full form in a new tab.

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

5.5 Labels

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, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 6. Troubleshooting.

5.5.1 Labels on task and ticket cards

Labels let you tag cards with custom metadata — e.g., "urgent", "in review", "customer feedback". They appear as colored chips on both the card front and in the detail modal.

5.5.1.1 View labels on a card

Open a card. If it has labels, they appear as colored chips in the modal. Each chip shows the label name; if there are many labels, extra ones collapse into a "+N" badge.

5.5.1.2 Assign a label to a card

Open the card and click the tag icon in the action bar at the top (if Assign labels permission is granted). A dialog appears with available labels. Check the box next to each label to assign it; uncheck to remove. Click Save to apply the changes.

5.5.1.3 Remove a label from a card

Open the card and click the tag icon to open the label assignment dialog. Uncheck the box next to a label to remove it. Click Save.

Note: Labels are project-wide (or global on the Kanban global view). They are not created per card — you can only assign existing labels. New labels are created in Setup by administrators.

Note: Only users with the Assign labels right can modify a card's labels. The tag icon is hidden for users without this right.

5.5.2 Label colors and appearance

5.5.2.1 Label color

Each label has a background color set by the administrator. The label name is written in black or white, whichever reads better on that colour. On the card front, labels are shown as chips; in the modal, they appear in two places: a row at the top of the action bar (capped at a few visible chips, with extras in a "+N" badge), and again in the full-width list in the label assignment dialog.

5.5.2.2 Labels in the dialogs

The Assign labels window and the global board's Filter by label window list each label as a chip in its own colour, the same chip as on the cards, so a label is recognised the same way everywhere.

Note: Label colors are chosen by administrators when creating a label in Setup. Colors are consistent across the board and all views.

5.5.3 Filtering the board by labels

On the Global Kanban view (when viewing all projects at once), you can filter cards to show only those with specific labels.

5.5.3.1 Open the label filter

Click the tag icon in the toolbar above the board (only visible when viewing the Global Kanban and labels are configured). A dialog opens showing all available labels.

5.5.3.2 Filter by one or more labels

Check the boxes next to the labels you want to see. The board immediately updates to show only cards with at least one of those labels. Click the filter icon again or a checkbox to change the filter.

5.5.3.3 Clear the label filter

Uncheck all labels to show all cards again, regardless of their labels.

Note: Label filtering is available only in the Global Kanban view. In single-project Kanban, labels are displayed but there is no separate filter UI for them.

Note: The label filter is saved per user, like other filters (project, user, group, card type). It is remembered across sessions.

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

6. Troubleshooting

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, 4.4 Notifications, 5.1 The board, 5.2 Working with cards, 5.3 Project task cards, 5.4 Ticket cards, 5.5 Labels.

A project doesn't appear on the Kanban board(s)

A project only has a board when it is a Kanban Ticket project, is not a template and is not in the trash. Check its type first on the project's Agile Project Management tab. On the global Kanban board, a project whose state is flagged Finished (Setup → Dropdowns → Project states) is also left out unless Show finished projects is switched on in the Filter projects window, and a project unticked in that window stays hidden until it is ticked again.

Card actions are missing or greyed out

Every card action (add, move, edit title, edit description, edit planned dates, delete, restore, permanently delete, assign a user, assign a label, edit the checklist, edit real dates, link tickets to a task, add a comment) is its own box under Administration → Profiles → a profile → Agile Project Management. None of them implies another, so a user missing one box loses exactly that one action and keeps the rest. Check the box for the missing action rather than assuming the whole board is locked. Deleting a ticket card also needs the right to update the project. A field you can't edit is greyed out and locked, with a tooltip, and a card you can't move can't be dragged at all.

A ticket card can't be moved to a column

This is expected. A ticket card's column follows the ticket's own status, so the board only lets you drag it to Pending, which puts the ticket on hold; any other drop is refused with a message. Assign, solve or close the ticket in its own form (the Open full form button in its card window), and its card moves to the matching column by itself.

A ticket is missing from the board

Tickets linked to one of the project's tasks, rather than to the project itself, have no card of their own until Show tickets linked to a task is switched on in the toolbar; they are always counted on their task's card. A closed ticket may also be one of the older closed cards that the Closed column only counts (see Closed cards shown in the configuration).

Labels, the checklist, real dates or the Tickets section are read-only

Each of these has its own box on the profile's Agile Project Management tab: Assign a label to a card, Edit a card checklist, Edit real dates and Link tickets to a task. Updating the plugin ticks new boxes once on the profiles that can update projects; if an administrator unticked one since, it stays unticked. Tick the box for the part that is read-only.

Real start or end dates stay empty

The board fills in the real dates only when a task is moved on the board. The Real start date is set when the task leaves the first column (or the No status column), and the Real end date when it reaches a column whose project state is flagged Finished (Setup → Dropdowns → Project states). A task edited elsewhere in GLPI, or moved into a state that is not flagged Finished, keeps its dates as they were. Moving a task back out of a finished column clears its end date. A user with Edit real dates can set either date by hand in the card window.

Hours look wrong, or a task shows as Late

The hours spent on a task are its Effective duration plus the time logged on the tickets linked to it (Tickets duration, read-only in the card window); hover the hours on the card to see the breakdown. A task is late when that total is over its Planned duration; a task with no planned duration is never late. Check that the task's planned duration is set and that time logged on its tickets was meant for this task.

A task's progress doesn't change on its own

Automatic progress only runs when Calculate task progress from tickets and checklist is on for the task's project. Check the project's Agile Project Management tab first: it can keep the global setting or switch it on or off for that project only, and the global value is shown next to the field. A task with neither linked tickets nor a checklist always keeps the percent typed by hand. A ticket counts as done only once it is solved or closed, and a checklist item once it is ticked.

A task's date is red or black

The date's colour compares today with the task's planned end, using the same thresholds as a ticket's Time to resolve: amber when the end is approaching, red when it is close, black once it has passed, or when the task finished after it. Change the planned end date if the plan has moved; this needs the Edit planned dates right.

Private comments are missing for some users

Whether a user sees a ticket card's private comments depends on GLPI's own See private ones right for followups, on the profile's Assistance tab, not on anything in the plugin's tab. A user with every Agile Project Management right but without that GLPI right never sees private comments on the board either.

A notification event never fires

Check three things, in order. First, the notification is still Active under Setup → Notifications → Notifications (search on item type Kanban). Second, it has a recipient who should receive this event: on install, every event notifies only the project's Manager, so team members get nothing until a recipient such as Project task team user is added on the notification's Recipients tab. Third, the recipient has a valid e-mail address.

A project state doesn't show up as a board column

A column exists only for a project state chosen in one of the six fields of the Kanban Ticket block of the configuration (Setup → General → Agile Project Management). Adding a state under Setup → Dropdowns → Project states does not add a column by itself. Cards whose state is not chosen there are not lost: they appear in the No status column at the far left of the board until their state is mapped or changed.

Followups written by the board have the wrong request source

Comments posted on a ticket card, and the followup written when a ticket card is moved to the Pending column, use the Request sources by default option of the configuration. Left empty, GLPI's own default request source applies, which may not be the one expected. Set it under Setup → General → Agile Project Management → General options.

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