Skip to main content
Built for working groups that need to track who is doing what. Replaces action-item lists in meeting minutes and message threads. An issue is a piece of work with an owner, a type, a priority and a status, discussed in a comment thread. Issues live on a project group: a group flagged as a project when it is created. The help desk uses the same board, scoped to the whole organisation instead of one group. Issue board for a project group with type, assignee, priority and status columns

​
Issues, tasks or the help desk

​
Creating a project group

Issues are not available on ordinary groups. You need a project group, and the Project Management module has to be on: Settings → Modules → Projects → Enable Project Management (needs ADMIN_TENANT). On the Issues page, a member who belongs to no project yet is offered Projects → New, which creates a group in project mode. Who may create one follows the tenant’s group-creation setting (Settings → Modules → Groups & Teams). Once the group exists, open it and pick the Issues tab. A new project group starts with: Both lists are editable afterwards. Open the group, choose Settings from its menu (/group/edit/{id}, group owner or group admin), and the Issue statuses and Issue types tabs sit under the group form. Add creates an entry, clicking a name opens it for renaming, the colour button beside it sets its colour, dragging a row reorders it on desktop, and the bin deletes it. The pencil beside Type and Status in the issue form is a shortcut to the same screen. Issue statuses tab on a project group's Settings screen, with the statuses listed as coloured tags and one row open for editing, showing its name field, colour picker, Save and Cancel buttons and the delete bin, beside the Issue types tab and the Add button The three field switches are the part that is still fixed: Priority field, Type field and Due date field are set when the group is created and have no editing screen. With the type field off, the Issue types tab is hidden along with the field itself.

​
Who sees what

Issues are visible to members of the group they belong to, and to nobody else. That check runs on the server, not just in the interface, so an issue in a private working group stays inside it. Anyone who can open a project board can add an issue to it and edit the issues on it.

​
Adding an issue

Click Add issue on the board. The form asks for: Mentioning someone in the description notifies them. The author follows the issue automatically and is notified of every comment.

​
The board

The board is a sortable list. Columns: due date where enabled, type, title, assignee, priority and status, plus a created-date-and-author column that the author button in the toolbar shows or hides. Type, status, assignee and priority can all be changed inline from the list. Filters sit above the list:
  • free-text search over the title
  • Task type
  • status: Opened (the default), any individual status, or Closed
  • assignee avatars, including unassigned
  • your own avatar, which filters to issues that mention you
  • an Author search, to see one person’s issues
Sorting by priority turns on drag-and-drop, so you can reorder issues by hand within the priority ranking. The board updates live as colleagues change things.

​
Closing an issue

Set the status dropdown to Close. Two variants:
  • Close archives the issue immediately and clears its status.
  • Close and comment opens a box for a closing note, then archives it.
Closed issues disappear from the default view and come back through the Closed status filter. Reopening means giving the issue a status again.

​
Comments and attachments

Every issue has a thread. Comments support rich text, images, video and file attachments, and mentions. Following an issue happens automatically when you create or comment on one.

​
Who gets notified

Changing status, type, priority or due date notifies nobody, and there is no reminder when a due date approaches. If you need due-date reminders, use tasks.

​
Common questions

The tab only appears on groups created in project mode, and only for members of the group. An ordinary group cannot be converted afterwards.
Rename, recolour, reorder or delete them on the group’s Settings screen, under Issue statuses, and add your own with Add. Statuses are per group, so changing them here affects only this project.
There is no kanban view. The board is a sortable list, with drag-and-drop reordering when you sort by priority.
No. An issue belongs to exactly one project group. Work that spans teams needs a shared group, or a project.
The due-date field is off for project groups by default and there is no screen to switch it on. Projects and tasks carry due dates as standard.
  • Help Desk - the same board for member support requests
  • Projects - the fuller project workspace with editable workflows
  • Tasks - task assignment, due dates and reminder digests
  • Groups - where project groups are created and managed
  • Notifications - controlling what reaches you