Operations

A simple issue tracker for a small team: one owner and one date per task, built in your CRM by your AI agent

An issue tracker for a small team is one list of work items, each with one owner, a status, a priority and a due date, plus a board and a short weekly review of what is overdue or blocked. Paste this template into your AI agent and it builds the list in Customermates, with projects, recurring chores and requests from outside the team. You approve the plan before anything is built.

No credit card required. First 14 days free.

How it works

  1. Get a workspace

    Create a free Customermates workspace with this template preselected, or use your own self-hosted instance.

    Start free trial

  2. Paste the prompt into your AI agent

    Copy the prompt below into Claude, ChatGPT or Codex, connected to your workspace. It reads your workspace first and proposes the setup in plain words.

  3. Approve the plan

    Nothing is written until you say yes. The agent creates no sample records, sends nothing and tells you what exists when it is done.

The prompt

One self-contained prompt. Choose where your workspace runs, then copy it.

 

What the agent creates

Lists, fields, stages, views and dashboard widgets, as the plan your agent proposes. You can rename or drop any part.

  • 4 lists
  • 19 fields
  • 6 views
  • 6 dashboard widgets
  • 8 follow-up rules
  • Requesters

    The people outside the team who ask for work.

    • Relation
    • Team
  • Projects

    A bundle of tasks with an owner, a health and a due date.

    • Status
    • Health
    • Owner
    • Due date
    • Repository link
  • Tasks

    One piece of work with one owner and one due date.

    • Status
    • Kind
    • Priority
    • Owner
    • Due date
    • Original due date
    • Done on
    • Blocked because
    • Link (pull request or ticket)
  • Recurring tasks

    A chore that comes back weekly, monthly, quarterly or yearly.

    • Repeats
    • Next due
    • Owner
  • Status

    1. Backlog
    2. To do
    3. In progress
    4. In review
    5. Blocked
    6. Done
    7. Cancelled
  • Status

    1. Planned
    2. Active
    3. On hold
    4. Done
    5. Cancelled

Views

  • All tasks
  • Task board
  • Blocked tasks
  • All projects
  • All recurring tasks
  • All requesters

Dashboard

  • Tasks by status
  • Open tasks by priority
  • Overdue tasks
  • Tasks due soon
  • Blocked tasks
  • Recent activity

The weekly team review in 30 minutes

The template builds the routine this work already has, so it keeps running after the setup.

  1. 1

    Open last week's list and start with what was promised: what is done and what slipped.

  2. 2

    Go through the overdue and blocked tasks and decide for each: recommit, de-scope or reassign. When a date slips, keep the original date and note the new one with a reason.

  3. 3

    Look at tasks that have not moved for five days and ask whether the task is vague or too large. Close the ones nobody needs.

  4. 4

    Triage new requests and bugs: give each a kind, a priority and an owner.

  5. 5

    End by reading the list back, so that every task has one named owner and one date before the meeting closes.

Follow-up rules

  • Notify the new owner when a task is assigned

    Automation ruleDue the same day

  • Notify the owner the day before a task is due

    Automation ruleDue the same day

  • Notify the lead the day after a task was due

    Automation ruleDue the same day

  • Notify the lead when a task stays blocked for 3 days

    Automation ruleDue the same day

  • Remind the owner when a task has not moved for 5 days

    Automation ruleDue the same day

  • Create a task when a recurring task comes due

    Automation ruleDue the same day

  • Create a task when the Git host sends an event

    Automation ruleDue the same day

  • Create a task and a requester when the request form is submitted

    Automation ruleDue after 2 days

Knowledge pages it seeds

Outlines for your own Knowledge Base, filled in with your facts. They are starting points, not finished policies.

  • How we work

    • Statuses, priorities and what done means
    • One owner and one date per task
  • Weekly review

    • Overdue, blocked and unassigned work
    • What changes this week
  • Triage of requests and bugs

    • Who decides what comes in
    • Severity versus priority

What it does not do

Know the limits before you start.

  • It is not a sprint or velocity tool: there are no sprints, story points or burn-down charts. A team that needs them should stay on Linear or Jira.
  • It is not a Gantt, dependency or capacity planner, a time tracker or a release manager.
  • It is not a code host, a CI system or a service desk with response-time clocks. A pull request or ticket link is a plain link field.
  • There is no native Slack or Teams integration and no mobile app. n8n is the route to Slack.
  • It is not an HR or performance-management system, and it has no single sign-on or field-level permissions.

Frequently asked questions

Can a simple tracker replace Trello, Jira or a spreadsheet?
For two to fifteen people who want one owner and one date per item, a weekly review and requests from outside the team on the same list, yes. Export your board or sheet to CSV or Excel and import it through the column-mapping wizard, or let your agent map and import it. If you need sprints, velocity or dependencies, stay on Linear, Jira or ClickUp.
Which statuses should a small team use?
Fewer than you think. Trello's To Do, Doing and Done and Linear's Backlog, Todo, In Progress, Done and Canceled are typical. The template starts from seven (Backlog, To do, In progress, In review, Blocked, Done, Cancelled) and you rename or drop any of them. Blocked earns its place because a blocked task otherwise goes unnoticed until its due date.
Should a team work in sprints or on a board?
Kanban guides lean on flow and on limiting work in progress, while Linear and Jira lean on sprints. This template uses a board plus a due date and has no sprint object, so a team that needs velocity should stay on a sprint tool.
Should stale tasks close automatically?
No. A reminder after five days without movement is safer than an automatic close, and meeting guides agree that stale items should be closed explicitly. The template reminds the owner and the owner decides. A task that stays open week after week is usually vague or too big, so fix the definition, not the person.
Does the agent message my team?
No. The prompt tells the agent to send nothing and to create no sample records. Drafts exist only when you ask for them, and you send them yourself.

Sources

The practice behind this template comes from these pages.

Customermates

Start your Team tracker today

Start a free trial, paste the prompt and approve the plan.

No credit card required. First 14 days free.