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.

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.