Skip to main content
Issues is a lightweight project management tool built into every group. Create tasks, assign them to members, track progress with statuses, and visualize work on a kanban board. No separate tool needed.

Do I need Issues?


Enabling Issues for a group

Issues are enabled per group, not globally:
  1. Go to the group’s settings
  2. Enable Issues/Tasks
  3. Configure which features are active

Creating an issue

Go to any group’s Issues tab → click Add Issue:

View modes

Backlog view

A flat list of all issues. Sort by date, priority, status, or assignee. Filter and search to find what you need. Good for reviewing everything at once.

Kanban view

A visual board with columns for each status. Drag issues between columns to update their status. See progress at a glance. Good for daily standups and active project tracking.

Customizing the workflow

Statuses

Default statuses: Create custom statuses to match your workflow: go to the group settings → Issue Statuses → add, rename, reorder, or color-code statuses.

Issue types

Default types: Create custom types in group settings → Issue Types. You can set default assignees per type — e.g., all “Budget” issues auto-assign to the treasurer.

Working with issues

Filtering

Filter by status, assignee, type, priority, due date, author, or creation date. Combine filters to focus on what matters — e.g., “High priority, assigned to me, In Progress.”

Notifications

Members get notified when:
  • They’re assigned to an issue
  • An issue they’re watching changes status
  • Someone comments on their issue
  • A due date is approaching

Common scenarios

Create issues during the meeting with clear subjects and assignees. Set due dates for accountability. Use a “Meeting Actions” type so you can filter by it later. Review open items at the start of the next meeting.
Keep it simple — 3 to 5 statuses is ideal. “To Do”, “In Progress”, and “Done” works for most teams. Add “In Review” if you have an approval step. More columns means more friction.
No — issues belong to one group. If multiple groups need to track work together, create a shared private group for the project and use issues there.
Issues are for internal team work — tasks, projects, action items among group members. Help Desk is for support — members submit tickets, a support team responds. Different workflows, different audiences.
Make it part of the routine. Review the board in meetings. Keep the workflow simple. If people find it burdensome, you probably have too many statuses or required fields.

  • Groups — Where issues live
  • Help Desk — Member support tickets
  • Files — Attach documents to issues