# Janet Agent
Source: https://docs.janet.ai/agent

Manage your work with natural language

<div>
  <div>
    <div>
      <div>
        <span>
          <svg>
            <path />
          </svg>

          Chat
        </span>

        <span>
          <svg>
            <path />

            <path />
          </svg>

          Docs
        </span>
      </div>

      <div>
        <span>
          <svg>
            <path />
          </svg>
        </span>

        <span>
          <svg>
            <path />

            <path />

            <path />
          </svg>
        </span>

        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>
          <svg>
            <path />
          </svg>
        </span>
      </div>
    </div>

    <div>
      <div>
        find all unassigned bugs related to login issues from the past 12 hours, assign them all to me, and create a prioritization plan doc
      </div>

      <div>
        <div>
          <span>search\_tickets</span>
        </div>

        <div>
          <span>search\_tickets</span>

          <span>
            <svg>
              <path />
            </svg>
          </span>
        </div>
      </div>

      <div>
        <div>
          <span>update\_tickets</span>
        </div>

        <div>
          <span>update\_tickets</span>

          <span>
            <svg>
              <path />
            </svg>
          </span>
        </div>
      </div>

      <div>
        <div>
          <span>create\_document</span>
        </div>

        <div>
          <span>create\_document</span>

          <span>
            <svg>
              <path />
            </svg>
          </span>
        </div>
      </div>

      <div>
        <p>Found 3 unassigned login bugs from the past 12 hours and assigned them all to you:</p>

        <div>
          <span>
            <span>
              <svg>
                <path />
              </svg>
            </span>

            <span>SW-84</span>
          </span>

          <span>SSO token refresh fails silently</span>
        </div>

        <div>
          <span>
            <span>
              <svg>
                <path />
              </svg>
            </span>

            <span>SW-71</span>
          </span>

          <span>OAuth callback timeout on mobile</span>
        </div>

        <div>
          <span>
            <span>
              <svg>
                <path />
              </svg>
            </span>

            <span>SW-63</span>
          </span>

          <span>Session cookie not persisting after redirect</span>
        </div>

        <div />

        <p>I also created <span><span><svg><path /><path /></svg></span><span>Login Bugs Triage Plan</span></span> with a prioritized breakdown of each issue and suggested next steps.</p>
        <p>Would you like me to add these to the current sprint, or create child tasks for each bug?</p>
      </div>
    </div>

    <div>
      <div>
        <div>
          <span>
            <img alt="" />

            <span>Sonnet 4.6</span>

            <svg>
              <path />
            </svg>
          </span>

          <span>
            <svg>
              <path />
            </svg>
          </span>
        </div>

        <div>
          <span>find all unassigned bugs related to login issues from the past 12 hours, assign them all to me, and create a prioritization plan doc</span>
          <span>@ for context, ask, update tickets</span>
        </div>

        <div>
          <div>
            <svg>
              <path />
            </svg>
          </div>

          <div>
            <svg>
              <path />
            </svg>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

All actions, from ticket creation and updates, to task reorganization and cleanup, to sprint planning and document drafting, can be done via the Janet Agent.

Accessible in the platform, Slack, and iMessage.

## Ask Janet

You can reach Janet Agent from anywhere in the dashboard without leaving the page you're on.

<CardGroup>
  <Card title="Ask Janet overlay" icon="sparkles">
    Click **Ask Janet** in the sidebar, or press **⌘⏎** (Ctrl+Enter) from any page, to open the agent overlay. Press **Esc** or click outside to close it.
  </Card>

  <Card title="Full page" icon="house">
    Open **Janet Agent** for the full-page experience. This is your default landing page.
  </Card>

  <Card title="Side panel" icon="sidebar">
    Open the **Chat** module in the right panel to talk to Janet alongside your current view.
  </Card>

  <Card title="Sessions" icon="clock-rotate-left">
    Every conversation, code run, and brainstorm is saved as a **session** you can return to.
  </Card>
</CardGroup>

The overlay, the full page, and the side panel all share the same conversations — start something in one and pick it back up in another.

### Sessions

Your work is organized into sessions, grouped into **Chats**, **Code runs** (builds), and **Brainstorm**. Search by title or key, rename or delete chats, and pin code runs you want to keep handy. Code runs that are waiting on you are flagged with a **Needs input** indicator.

### The composer

When you message Janet you can:

* **Add context** with `@` to mention tickets, projects, documents, and people.
* **Attach files** — images, PDFs, text, audio, or video.
* **Pick a model** per message: Opus 4.8, Sonnet 4.6 (default), or Haiku 4.5.
* Use **prompt templates** for common requests like triaging open tickets.
* Send a message straight to your org's JanetClaw with the **`/janetclaw`** command.

Janet asks for confirmation before running actions that change your workspace, and pauses to ask clarifying questions when it needs a decision from you.

### Beyond chat

<CardGroup>
  <Card title="Brainstorm" icon="waveform-lines" href="/features/brainstorm">
    Record a conversation and let Janet capture notes, action items, and ticket proposals.
  </Card>

  <Card title="Code Runs" icon="code" href="/ticket-features/code-runs">
    Ask Janet to build something, or send a ticket to Claude Code to open a draft PR.
  </Card>
</CardGroup>

### What you can do

<CardGroup>
  <Card title="Search" icon="magnifying-glass">
    Filter by status, assignee, priority, type, tags, or dates. Search by meaning with semantic search. Get full ticket details with comments and child tasks.
  </Card>

  <Card title="Tickets" icon="ticket">
    Create, update, and delete tickets. Bulk update many at once. Move and reorder within columns. Schedule tickets to activate at a future time.
  </Card>

  <Card title="Sprints" icon="forward">
    Create and manage sprints. Add, remove, and reorder tickets within sprints.
  </Card>

  <Card title="Child Tasks" icon="list-check">
    Create and manage child tasks on any ticket.
  </Card>

  <Card title="Comments" icon="comment">
    Add, edit, and delete comments on any ticket.
  </Card>

  <Card title="Documents" icon="file-lines">
    Create, read, and update org-wide or private documents.
  </Card>

  <Card title="Web search" icon="globe">
    Search the web for current information when you need context outside your workspace.
  </Card>

  <Card title="Multi-step actions" icon="layer-group">
    Chain any of the above in a single request. The agent handles the sequencing automatically.
  </Card>
</CardGroup>


# Brainstorm
Source: https://docs.janet.ai/features/brainstorm

Record a conversation out loud and let Janet capture notes, action items, and ticket proposals

<div>
  <video aria-label="Brainstorm recording with live capture timeline" />
</div>

**Brainstorm** records a conversation: a meeting, a planning session, or thinking out loud. Janet listens live. As you talk, Janet builds a running capture of the insights, decisions, and actions that matter. When you stop, it saves a notes document and proposes tickets for you to review.

Brainstorm is part of [Janet Agent](/agent): each brainstorm is a chat session you can keep talking to.

## Start a brainstorm

<CardGroup>
  <Card title="Janet Agent home" icon="house">
    On the Janet Agent home page, click **Record a meeting** in the composer toolbar to start a new brainstorm session.
  </Card>

  <Card title="Ask Janet overlay" icon="sparkles">
    Open the [Ask Janet overlay](/agent) (⌘⏎), switch to the **Brainstorm** tab, and click **Start Recording**.
  </Card>

  <Card title="Inside a chat" icon="comment">
    In a full page chat session, click **Record a meeting** (the mic) in the composer to begin recording in that session.
  </Card>

  <Card title="Sidebar" icon="list">
    Find past brainstorms under the **Brainstorm** tab in the sessions list, or start a fresh one with **New**.
  </Card>
</CardGroup>

New sessions are titled `Brainstorm {date}` by default, which you can edit.

## While you record

As you speak, Janet transcribes the conversation and shows **What Janet's capturing**: a live timeline of moments grouped into **Insights**, **Decisions**, and **Actions**. The raw transcript stays hidden; the timeline is the live view.

You can:

* **Ask Janet while you record**: type in the composer to ask questions or give direction without interrupting the recording.
* **Pause** and **Resume**: pause to review what was captured or to ask Janet to fix something, then resume.
* **Discard**: throw away the session.
* **Stop & save**: finish and generate your notes and proposals.

<Note>
  Ticket proposals are prepared in the background while you record but are only presented for review after you stop and save.
</Note>

### Microphone and consent

Brainstorm needs microphone access. If your browser blocks the mic, allow it for the site and reload. When a session records raw audio (used for speaker attribution), Janet shows a reminder that everyone present should agree to be recorded.

For the best transcription with speaker labels, Brainstorm uses live streaming transcription. If that isn't available, it falls back to your browser's built-in speech recognition (Chrome or Edge).

## What you get when you save

When you stop and save, Janet produces:

| Output               | Description                                                                                                                                                                               |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Notes document**   | A document with the transcript, summary, and action items. It appears in [Documents](/features/documents) with a **Brainstorm** badge. Open it from **Open document** in the review card. |
| **Summary**          | A short recap of the conversation.                                                                                                                                                        |
| **Action items**     | The action items Janet captured.                                                                                                                                                          |
| **Ticket proposals** | Proposed ticket changes (**New** tickets, **Status** changes, or description **Append**s) that you **Accept** or **Dismiss**.                                                             |

After saving, Janet starts a review in the chat (**Let's confirm what I captured**) so you can walk through the notes and proposals together and ask follow-up questions.


# Documents
Source: https://docs.janet.ai/features/documents

Create and manage collaborative documents with Janet Agent, MCP, or the editor

Documents give you and your agents a shared place for specs, notes, and decisions. [Janet Agent](/agent) can work with them in chat, while connected MCP clients can use the [Janet MCP server](/mcpserver). Changes appear live when the document is open.

<div>
  <div>
    <div>
      <div>
        <div>
          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>

          <span>Push Notification Redesign</span>
          <span>editor</span>
        </div>

        <div>
          <div>
            <img alt="" />

            <img alt="" />
          </div>

          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>

          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>
        </div>
      </div>

      <div>
        <div>Push Notification Redesign</div>
        <div>Overview</div>
        <div>Redesign the push notification system to support per-channel preferences and batched delivery. Related tickets: <span><span><svg><path /></svg></span>MOB-38</span> <span><span><svg><path /></svg></span>MOB-12</span></div>
        <div>Requirements</div>
        <div>Users can toggle notifications per channel (Slack, email, in-app) <span><span>Will</span></span></div>
        <div>Batch low-priority alerts into a single daily digest</div>
        <div>Critical alerts (P0/P1) always deliver immediately</div>
        <div>Open Questions</div>
        <div><span><img alt="" />Adhit Sankaran</span> — should we migrate existing prefs or reset to defaults? <span><span>Adhit</span></span></div>
        <div>Rate limit strategy for webhook delivery — see <span><span><svg><path /></svg></span>MOB-27</span></div>
        <div><span><img alt="" />Will Barthell</span> to confirm API contract with mobile team</div>
      </div>
    </div>
  </div>
</div>

## Work with documents using agents

Ask Janet Agent to find a document or change one in natural language. MCP clients can use the same document capabilities directly.

| Task                                      | MCP tool                                 |
| ----------------------------------------- | ---------------------------------------- |
| List accessible documents                 | `list_documents`                         |
| Read a document                           | `get_document`                           |
| Create a private or organization document | `create_document`                        |
| Change the title or content               | `update_document`                        |
| Soft-delete or recover a document         | `delete_document` and `restore_document` |

Document tools follow your Janet permissions. An agent can only read documents you can access. Only the owner can delete or restore a document.

<Note>
  When you call `update_document` through MCP, send the complete Markdown body. The new content replaces the whole document rather than patching one section.
</Note>

### Use documents as agent context

The `search_tickets_semantic` tool includes document content when you search without a project filter. This lets an agent find relevant specs or meeting notes alongside tickets.

You can also attach a Janet document to a ticket with `add_context_to_tickets` by setting `type` to `document`. To show the same document under another page without moving it, use `add_document_shortcut`.

## Find and organize documents

Open **Documents** from the sidebar. Use **All**, **Private**, **Shared with Me**, or **Organization** to filter the list. Press **⌘K** to search by title or content. Press **c** to create a document.

Use folders to group related documents. Folders can be private or available to the organization, and their access rules apply to the documents inside them. You can nest folders or drag a document into one.

Synced [meeting notes](/integrations/note-takers) are grouped into read-only folders by provider. Documents created from a [brainstorm](/features/brainstorm) show a **Brainstorm** source badge.

## Edit and collaborate

Create a document from the **Create** menu, then choose **Private** or **Organization** visibility. The editor supports rich text and images. It also supports syntax-highlighted code blocks.

Type `/` to open formatting and embed commands. Type `@` to link tickets or other documents. You can also mention people and projects.

Other editors appear with live cursors. You can leave comments and filter them by open or resolved. Local edits sync after you reconnect if your connection drops.

## Share documents

Owners have full control. Editors can change content and invite other people, while viewers have read-only access. Organization documents are visible to everyone in the organization, and organization admins can edit them.


# Welcome to Janet AI
Source: https://docs.janet.ai/index

Janet AI is the **intelligent product management system** built for modern teams. Janet tracks and manages your work automatically so you can focus on building.

<div>
  <div>
    <div>
      <div>
        <div><div><span>PROJ-142</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Users getting 500 errors on checkout when applying discount codes over \$50</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-136</span><svg><rect /><rect /><rect /></svg></div><div>Add WebSocket presence indicators showing who's viewing each ticket in real time</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-131</span><svg><rect /><rect /><rect /></svg></div><div>Migrate payment webhooks from Stripe v2 to v3 event schema</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-128</span><svg><rect /><rect /><rect /></svg></div><div>Document rate limiting behavior and retry headers for public API v2 endpoints</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-125</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Race condition in JWT refresh causes 401 cascade across microservices</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-122</span><svg><rect /><rect /><rect /></svg></div><div>Redesign settings page responsive layout for iPad and tablet viewports</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-119</span><svg><rect /><rect /><rect /></svg></div><div>Configure GitHub Actions CI with parallel test runners for staging deploys</div><div>        <img alt="" /></div></div>

        <div><div><span>PROJ-142</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Users getting 500 errors on checkout when applying discount codes over \$50</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-136</span><svg><rect /><rect /><rect /></svg></div><div>Add WebSocket presence indicators showing who's viewing each ticket in real time</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-131</span><svg><rect /><rect /><rect /></svg></div><div>Migrate payment webhooks from Stripe v2 to v3 event schema</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-128</span><svg><rect /><rect /><rect /></svg></div><div>Document rate limiting behavior and retry headers for public API v2 endpoints</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-125</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Race condition in JWT refresh causes 401 cascade across microservices</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-122</span><svg><rect /><rect /><rect /></svg></div><div>Redesign settings page responsive layout for iPad and tablet viewports</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-119</span><svg><rect /><rect /><rect /></svg></div><div>Configure GitHub Actions CI with parallel test runners for staging deploys</div><div>        <img alt="" /></div></div>
      </div>
    </div>

    <div>
      <div>
        <div><div><span>PROJ-117</span><svg><rect /><rect /><rect /></svg></div><div>Slack bot drops messages when channel has more than 500 members</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-114</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Database connection pool exhausted under load causing cascading timeouts</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-111</span><svg><rect /><rect /><rect /></svg></div><div>Build dark mode color token system with CSS custom properties for theming</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-108</span><svg><rect /><rect /><rect /></svg></div><div>Add CSV export option for filtered ticket views with custom column selection</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-105</span><svg><rect /><rect /><rect /></svg></div><div>Email notifications sending duplicate digests when user belongs to multiple orgs</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-102</span><svg><rect /><rect /><rect /><rect /></svg></div><div>WebSocket reconnection loop after deploying new API gateway version</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-99</span><svg><rect /><rect /><rect /></svg></div><div>Implement granular RBAC permissions for project-level admin actions</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-96</span><svg><rect /><rect /><rect /></svg></div><div>Optimize N+1 query in ticket list endpoint causing 3s response times</div><div>        <img alt="" /></div></div>

        <div><div><span>PROJ-117</span><svg><rect /><rect /><rect /></svg></div><div>Slack bot drops messages when channel has more than 500 members</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-114</span><svg><rect /><rect /><rect /><rect /></svg></div><div>Database connection pool exhausted under load causing cascading timeouts</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-111</span><svg><rect /><rect /><rect /></svg></div><div>Build dark mode color token system with CSS custom properties for theming</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-108</span><svg><rect /><rect /><rect /></svg></div><div>Add CSV export option for filtered ticket views with custom column selection</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-105</span><svg><rect /><rect /><rect /></svg></div><div>Email notifications sending duplicate digests when user belongs to multiple orgs</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-102</span><svg><rect /><rect /><rect /><rect /></svg></div><div>WebSocket reconnection loop after deploying new API gateway version</div><div>        <img alt="" /></div></div>
        <div><div><span>PROJ-99</span><svg><rect /><rect /><rect /></svg></div><div>Implement granular RBAC permissions for project-level admin actions</div><div><img alt="" /><img alt="" /></div></div>
        <div><div><span>PROJ-96</span><svg><rect /><rect /><rect /></svg></div><div>Optimize N+1 query in ticket list endpoint causing 3s response times</div><div>        <img alt="" /></div></div>
      </div>
    </div>
  </div>
</div>

## What Makes Janet Different

Janet doesn't wait for manual updates. It works in the background, tracking conversations, updating tickets, and keeping your projects organized.

**Janet auto-tracks** issues from Slack, Discord, SMS, and email so nothing falls through the cracks. **Janet enriches tickets** with auto-generated descriptions, smart tagging, related issue clustering, suggested assignees and priorities, duplicate detection, and continuous quality improvements. **Janet auto-moves** tickets as GitHub PRs are opened and merged. **The Janet Agent** can create tickets, update statuses, reorganize boards, plan sprints, and draft documents — accessible from Slack, SMS, and directly in the platform. **The Janet MCP Server** brings this same power to Claude and Cursor, so your coding agents can create, update, and resolve issues.

## Get Started

<Card title="Quickstart" icon="rocket" href="/quickstart">
  Set up your first project
</Card>


# GitHub
Source: https://docs.janet.ai/integrations/github

Automatically move tickets as Pull Requests are opened and merged

Connect your GitHub repos to Janet AI so tickets move automatically when PRs are opened and merged.

<div>
  <div>
    <div>
      <div>
        <div>INTEGRATION SETTINGS</div>

        <div>
          <div>
            <img alt="" />

            GitHub

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Repositories</div>
            <div>Accounts</div>
            <div>PR Events</div>
            <div>Danger Zone</div>
          </div>

          <div>
            <img alt="" />

            Slack
          </div>

          <div>
            <img alt="" />

            Discord
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <svg>
              <path />
            </svg>
          </div>

          <div>
            <span>
              <span>GitHub</span>
            </span>

            <div>
              <svg>
                <path />

                <path />
              </svg>

              <span>Connected as [will@acme.com](mailto:will@acme.com)</span>
            </div>
          </div>
        </div>

        <div>
          <span>Your Repos</span>
          <span>Team Repos</span>

          <span>
            <svg>
              <path />
            </svg>

            Add Repository
          </span>
        </div>

        <div>
          <div>
            <div>
              <svg>
                <path />
              </svg>
            </div>

            <div>
              <div>acme/frontend</div>
              <div>Mobile App · main</div>
            </div>

            <span><span />Active</span>

            <div>
              <span>
                <svg>
                  <path />

                  <path />
                </svg>
              </span>

              <span>
                <svg>
                  <path />
                </svg>
              </span>
            </div>
          </div>

          <div>
            <div>
              <svg>
                <path />
              </svg>
            </div>

            <div>
              <div>acme/api</div>
              <div>Backend API · main</div>
            </div>

            <span><span />Active</span>

            <div>
              <span>
                <svg>
                  <path />

                  <path />
                </svg>
              </span>

              <span>
                <svg>
                  <path />
                </svg>
              </span>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## Setup

Go to **Integrations -> GitHub**, click **Connect**, and install the Janet AI GitHub App. Then click **Add Repository** to link a repo to a project.

| Setting           | What to Choose                                               |
| ----------------- | ------------------------------------------------------------ |
| Repository        | The repo to monitor                                          |
| Production Branch | Usually `main` -- only PRs to this branch trigger automation |
| Project           | Which Janet project to update                                |
| When PR Opens     | Column to move tickets to (default: "In Review")             |
| When PR Merges    | Column to move tickets to (default: "Done")                  |

Use **Link Another Project** to map the same repo to multiple projects.

## How It Works

When a PR is opened, Janet AI matches it to a ticket -- either by explicit mention (`fixes PROJ-123`) or by semantic search across active tickets. The matched ticket moves to your configured column automatically.

<div>
  <div>
    <div>
      <div>
        <div>INTEGRATION SETTINGS</div>

        <div>
          <div>
            <img alt="" />

            GitHub

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Repositories</div>
            <div>Accounts</div>
            <div>PR Events</div>
            <div>Danger Zone</div>
          </div>

          <div>
            <img alt="" />

            Slack
          </div>

          <div>
            <img alt="" />

            Discord
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <svg>
              <path />
            </svg>
          </div>

          <div>
            <span>
              <span>GitHub</span>
            </span>

            <div>
              <svg>
                <path />

                <path />
              </svg>

              <span>Connected as [will@acme.com](mailto:will@acme.com)</span>
            </div>
          </div>
        </div>

        <div>
          <div><span>Merged</span><span>cleanup expired org invites from database</span><span><svg><rect /><path /></svg><span>1</span><span>1d ago</span></span></div>
          <div><span>Merged</span><span>fix cost tracking entry points + env vars</span><span><svg><rect /><path /></svg><span>2</span><span>1d ago</span></span></div>
          <div><span>Opened</span><span>add rate limiter to public API endpoints</span><span><span>2d ago</span></span></div>
          <div><span>Merged</span><span>bug fix: agent failing to read user created docs</span><span><svg><rect /><path /></svg><span>1</span><span>2d ago</span></span></div>
          <div><span>Merged</span><span>auto-nav to repos tab after github install</span><span><svg><rect /><path /></svg><span>1</span><span>3d ago</span></span></div>
        </div>
      </div>
    </div>
  </div>
</div>

## Auto-Create Tickets

Enable **"Create ticket if no match found"** in your repo config. Janet AI will create a new ticket from the PR title and place it in your configured column -- all the same automation still applies.

## Multiple Accounts

Connect additional GitHub accounts via **Settings -> Add Account** for personal + work GitHub or multiple organizations.

<div>
  <div>
    <div>
      <div>
        <div>INTEGRATION SETTINGS</div>

        <div>
          <div>
            <img alt="" />

            GitHub

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Repositories</div>
            <div>Accounts</div>
            <div>PR Events</div>
            <div>Danger Zone</div>
          </div>

          <div>
            <img alt="" />

            Slack
          </div>

          <div>
            <img alt="" />

            Discord
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <svg>
              <path />
            </svg>
          </div>

          <div>
            <span>
              <span>GitHub</span>
            </span>

            <div>
              <svg>
                <path />

                <path />
              </svg>

              <span>2 accounts connected</span>
            </div>
          </div>
        </div>

        <div>
          <span>
            <svg>
              <path />
            </svg>

            Add Account
          </span>
        </div>

        <div>
          <div>
            <div>
              <svg>
                <path />
              </svg>
            </div>

            <div>
              <div>willcraft</div>
              <div>[will@acme.com](mailto:will@acme.com) · Connected Mar 12</div>
            </div>

            <span>Disconnect</span>
          </div>

          <div>
            <div>
              <svg>
                <path />
              </svg>
            </div>

            <div>
              <div>will-personal</div>
              <div>[will@gmail.com](mailto:will@gmail.com) · Connected Mar 28</div>
            </div>

            <span>Disconnect</span>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## FAQ

<AccordionGroup>
  <Accordion title="Can multiple people configure the same repository?">
    Yes, to different projects. The same repo-project combination can only exist once.
  </Accordion>

  <Accordion title="Do all team PRs trigger automation?">
    Yes. Any developer's PR triggers it, not just yours.
  </Accordion>

  <Accordion title="Can one repo update multiple projects?">
    Yes. Click "Link Another Project" when configuring.
  </Accordion>

  <Accordion title="Can I skip automation for a specific PR?">
    Include `#janet-ignore` in the PR title or description. Janet AI will skip it entirely.
  </Accordion>

  <Accordion title="Why are tickets with my PRs not getting auto-assigned to me?">
    Janet AI identifies PR contributors by commit email. If your commit email is anonymized (e.g. `123456+username@users.noreply.github.com`), Janet can't match it to your account.

    **GitHub.com:**

    1. Click your profile picture -> **Settings**
    2. In the **Access** section, click **Emails**
    3. Add and verify your email address
    4. Set it as your **Primary email address**
    5. Make sure **"Keep my email addresses private"** is **Off**

    For the full guide see: [Mac](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address?platform=mac#setting-your-commit-email-address-on-github) / [Windows](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address?platform=windows#setting-your-commit-email-address-on-github)

    **GitHub Desktop:**

    On Mac: **GitHub Desktop** (menu bar) -> **Settings** -> **Git**

    On Windows: **File** -> **Options** -> **Git**

    Select the email you use with Janet AI in the **Email** dropdown.

    For the full guide see: [Mac](https://docs.github.com/en/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop?platform=mac#configuring-your-global-author-information) / [Windows](https://docs.github.com/en/desktop/configuring-and-customizing-github-desktop/configuring-git-for-github-desktop?platform=windows#configuring-your-global-author-information)

    **Command line:**

    ```bash theme={null}
    git config --global user.email "YOUR_EMAIL"
    ```

    For the full guide see: [Mac](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address?platform=mac#setting-your-commit-email-address-in-git) / [Windows](https://docs.github.com/en/account-and-profile/how-tos/email-preferences/setting-your-commit-email-address?platform=windows#setting-your-commit-email-address-in-git)
  </Accordion>
</AccordionGroup>


# Meeting Notes
Source: https://docs.janet.ai/integrations/note-takers

Sync meeting transcripts and summaries from your note taker, and turn action items into tickets

<div>
  <div>
    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>GitHub</div>
        <div>Create and update tickets from Pull Requests</div>
      </div>
    </div>

    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>Slack</div>
        <div>Create and update tickets from Slack messages</div>
      </div>
    </div>

    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>Meeting Notes</div>
        <div>Save transcript & notes in documents and turn them into tickets</div>
      </div>

      <span>
        <span />

        Connected
      </span>
    </div>

    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>Messages (SMS)</div>
        <div>Create and update tickets via text</div>
      </div>
    </div>
  </div>
</div>

Connect a meeting note taker so every meeting transcript and summary is saved to your private **Meeting Notes** documents automatically. Action items become tickets you review before they're created.

<Callout icon="lightbulb">
  Meeting Notes replaces the Google Calendar integration. If you don't already use a note taker, [Granola](https://granola.ai)'s free Basic plan supports everything you need.
</Callout>

## How it works

After you connect a provider, Janet:

1. Ingests each meeting's transcript and summary into a **Meeting Notes** document, grouped by provider.
2. Extracts action items and surfaces them as **proposed ticket changes**.
3. Lets you review each proposal and **Accept** or **Dismiss** it before any ticket is created or updated.

Meeting Notes integrations are connected **per user**. Each person connects their own note taker.

## Supported providers

| Provider         | How it connects                             | Self serve |
| ---------------- | ------------------------------------------- | ---------- |
| **Granola**      | Janet pulls your notes on demand            | Yes        |
| **Fireflies.ai** | Provider pushes notes to Janet via webhook  | Yes        |
| **Fellow\.ai**   | Request an integration and Janet sets it up | No         |
| **Otter.ai**     | Request an integration and Janet sets it up | No         |

Don't see your note taker? In the setup wizard, choose **Don't see your preferred note taker?** and tell Janet which one you'd like. For example tl;dv, Avoma, or Notion AI. The team will prioritize it.

## Connect a note taker

Open **Integrations → Meeting Notes** to launch the setup wizard.

<div>
  <div>
    <div>
      <span>1</span>

      <span />
    </div>

    <div>
      <div>Choose your provider</div>
      <p>Select Granola, Fireflies.ai, Fellow\.ai, or Otter.ai.</p>

      <div>
        <div>
          <div>
            <div>
              <div>
                <span>
                  <img alt="" />
                </span>

                <span>Meeting Notes</span>
              </div>

              <div>
                <img alt="" />

                <div>
                  <span>Granola</span>
                  <span>AI notepad for back to back meetings.</span>
                </div>

                <span />
              </div>

              <div>
                <img alt="" />

                <div>
                  <span>Fireflies.ai</span>
                  <span>Records, transcribes, and summarizes meetings.</span>
                </div>

                <span />
              </div>
            </div>

            <span>
              <svg>
                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>
    </div>
  </div>

  <div>
    <div>
      <span>2</span>

      <span />
    </div>

    <div>
      <div>Add your API key (Granola and Fireflies)</div>
      <p>Paste your provider API key and click <strong>Connect</strong>. For Fireflies you can also add an optional <strong>signing secret</strong> to verify webhook signatures.</p>
      <p>Fellow\.ai and Otter.ai aren't self serve yet. Instead, click <strong>Request integration</strong> and the team will set it up for you. A workspace admin must enable the provider's API key and webhook feature first.</p>

      <div>
        <div>
          <div>
            <div>
              <div>Granola API key</div>

              <div />

              <div>Required. Janet uses it to pull your notes from Granola on demand.</div>

              <div>
                <span>Connect</span>
              </div>
            </div>

            <span>
              <svg>
                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>
    </div>
  </div>

  <div>
    <div>
      <span>3</span>
    </div>

    <div>
      <div>Set up the webhook (Fireflies)</div>
      <p>After connecting a webhook based provider, copy your <strong>ingest URL</strong> (it includes your secret key) and paste it into the provider's webhook settings.</p>
      <p>You can rotate the secret later from the integration's <strong>Settings</strong> tab if needed.</p>

      <div>
        <div>
          <div>
            <div>
              <div>Ingest URL</div>

              <div>
                <span>[https://api.janet.ai/ingest/ff…](https://api.janet.ai/ingest/ff…)</span>
                <span>Copy</span>
                <span>Copied</span>
              </div>
            </div>

            <span>
              <svg>
                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

### Provider setup notes

* **Granola** doesn't push notes automatically. After a meeting, ask Janet to "pull my latest Granola notes", or use **Pull latest notes** on the integration's **Settings** tab. They'll be saved to Meeting Notes.
* **Fireflies** sends the transcript and summary to Janet automatically when transcription completes. Set its **Webhook URL** to your Janet ingest URL.

## Where your meeting notes appear

<CardGroup>
  <Card title="Documents" icon="folder">
    Each meeting becomes a private document under a provider folder (Granola, Fireflies, and so on) in [Documents](/features/documents). Provider folders are read only groupings.
  </Card>

  <Card title="Meeting Notes widget" icon="table-cells">
    Add the **Meeting notes** widget to a [Views dashboard](/views/dashboard) to see your most recently synced notes, optionally scoped to a project.
  </Card>

  <Card title="Meetings tab" icon="calendar">
    The integration's **Meetings** tab lists every meeting with its date, attendees, and ticket extraction status.
  </Card>

  <Card title="Meeting details" icon="list">
    Open any meeting to see its transcript, attendees, the notes document, and the tickets created from it.
  </Card>
</CardGroup>

## Action items into tickets

When a transcript is ingested, Janet runs ticket extraction and proposes changes for you to review:

* **New**: create a ticket with a title, description, project, priority, and status.
* **Edited**: update an existing ticket's status or append details to its description.

Open&#x20;**&#x20;change(s) to review** on a meeting to see the **Proposed ticket changes**. Choose **Accept** or **Dismiss** per proposal, or **Accept all** / **Dismiss all**. Approved proposals appear under **Tickets from this meeting** with links to each ticket.

<Note>
  Nothing is created automatically. Action items always surface as proposals that you approve first.
</Note>

## Manage your integration

Each connected provider has its own entry with three tabs:

* **Settings**: view connection status, configured API key, and sync activity. Rotate the webhook secret, replace the API key, or (for Granola) pull the latest notes.
* **Meetings**: browse synced meetings and review ticket proposals.
* **Danger Zone**: disconnect the provider. Janet stops receiving new notes and the webhook secret stops working, but meeting documents already created are kept.

### Add participants

From a meeting's details panel, use **Add participant** to grant a teammate access to that meeting, its notes document, and its ticket proposals.


# Slack
Source: https://docs.janet.ai/integrations/slack



Capture reports via emoji reactions and slash commands, and chat with Janet AI directly in Slack threads. Navigate to **Integrations → Slack** to install.

## Slash Commands

Workspace members use `/bug-report` and `/feature-request` to submit reports that Janet AI processes into tickets.

<div>
  <div>
    <div>
      <div>
        <div>INTEGRATION SETTINGS</div>

        <div>
          <div>
            <img alt="" />

            GitHub
          </div>

          <div>
            <img alt="" />

            Slack

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Slash Commands</div>
            <div>Emoji Reactions</div>
            <div>Danger Zone</div>
          </div>

          <div>
            <img alt="" />

            Discord
          </div>

          <div>
            <img alt="" />

            Email
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <img alt="Slack" />
          </div>

          <div>
            <span>Acme Inc Workspace</span>
            <span>Connected</span>
          </div>
        </div>

        <div>
          <div>Slash Commands</div>
          <div>When workspace members use these commands, a modal appears to submit a report.</div>

          <div>
            <div>
              <span>/bug-report</span>
              <span>→</span>
              <span>Mobile App</span>
            </div>

            <div>
              <span>/feature-request</span>
              <span>→</span>
              <span>Mobile App</span>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## Emoji Reactions

React to any Slack message with a configured emoji to instantly create a ticket — no commands needed. Navigate to **Integrations → Slack → Emoji Reactions** to set up rules mapping emojis to projects and columns. Configure **reactor scope** per rule: org members only or anyone including external connections.

<div>
  <div>
    <div>
      <div>
        <div>INTEGRATION SETTINGS</div>

        <div>
          <div>
            <img alt="" />

            GitHub
          </div>

          <div>
            <img alt="" />

            Slack

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Slash Commands</div>
            <div>Emoji Reactions</div>
            <div>Danger Zone</div>
          </div>

          <div>
            <img alt="" />

            Discord
          </div>

          <div>
            <img alt="" />

            Email
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <img alt="Slack" />
          </div>

          <div>
            <span>Acme Inc Workspace</span>
            <span>Connected</span>
          </div>
        </div>

        <div>
          <div>
            <div>
              <div>Emoji Reactions</div>
              <div>React to Slack messages to auto-create tickets.</div>
            </div>

            <span>
              <svg>
                <path />
              </svg>

              Add Rule
            </span>
          </div>

          <div>
            <div>
              <span>🎫</span>
              <span>Mobile App <code>MOB</code></span>
              <span>Backlog</span>
            </div>

            <div>
              <span>🔴</span>
              <span>Mobile App <code>MOB</code></span>
              <span>Urgent</span>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## Janet AI in Slack

`@mention` the bot in any Slack thread to use all of [Janet Agent's](/agent) capabilities — create tickets, search, update, comment — without leaving Slack. Each thread syncs with your Janet AI chat history.

<div>
  <div>
    <div>
      <span>Thread</span>

      <span>
        <svg>
          <path />
        </svg>
      </span>
    </div>

    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>
          <span>Adhit Sankaran</span>
          <span>10:24 AM</span>
        </div>

        <div>
          <span>@Janet AI</span> look through the backlog and find quick wins we can knock out this week, then create a sprint for them
        </div>

        <div>
          <span><span>👍</span> 2</span>
        </div>
      </div>
    </div>

    <div>
      <span>1 reply</span>
    </div>

    <div>
      <div>
        <img alt="" />
      </div>

      <div>
        <div>
          <span>Janet AI</span>
          <span>APP</span>
          <span>10:24 AM</span>
        </div>

        <div>Found 5 quick wins in the backlog:</div>

        <div>
          <span>- <span>MAIN-434</span> \[Backlog] "Enrich sparse tickets" (Medium, <span>@adhit.sankaran</span>)</span>
          <span>- <span>MAIN-612</span> \[Backlog] "Send notifications to SMS" (Medium)</span>
          <span>- <span>MAIN-991</span> \[Backlog] "Test project name resolution" (Low)</span>
          <span>- <span>MAIN-101</span> \[Backlog] "Teams integration" (Low, <span>@will.barthell</span>)</span>
          <span>- <span>MAIN-1136</span> \[Backlog] "Improve AI insights page" (Medium)</span>
        </div>

        <div>Created sprint 'Quick Wins — Apr 2' (2026-04-02 to 2026-04-09) and added all 5 tickets.</div>
        <div>Want me to assign these out across the team or adjust priorities?</div>
      </div>
    </div>
  </div>
</div>


# JanetClaw
Source: https://docs.janet.ai/janetclaw

Set up and use your cloud-hosted AI project manager

<div>
  <div>
    <img alt="" />

    <div>
      <div>JanetClaw</div>
      <div>Your always-on AI project manager</div>
    </div>

    <span>
      <svg>
        <path />
      </svg>
    </span>
  </div>
</div>

JanetClaw is a cloud-hosted AI teammate that works in the background and responds when you message it. It turns conversations into tickets and keeps existing work updated. It can also prepare briefings or carry out repeatable workflows. Each assistant runs in an isolated cloud pod with its own memory and permissions.

Open **JanetClaw** from the Janet sidebar to set it up or manage it.

## How JanetClaw works

Your organization starts with a team assistant. You can add a separate customer support assistant after the team assistant is live.

| Where you use it                   | What happens                                                                                                                                            |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Slack DM**                       | You have a private conversation with JanetClaw.                                                                                                         |
| **Internal Slack channel**         | Mention `@JanetClaw` to use the shared team assistant. It acts with your Janet permissions, so its actions are attributed to you.                       |
| **Enrolled Slack Connect channel** | External customers can talk to the customer support assistant. It can work with tickets, but it cannot use member credentials or other connected tools. |

JanetClaw only responds to external customers in Slack Connect channels that an admin has enrolled.

## What you can do

| Use case                 | Example                                                                                                                                                |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Manage tickets**       | Create a ticket from a Slack message or email. JanetClaw attaches the source as context and updates a matching ticket instead of creating a duplicate. |
| **Get project context**  | Ask JanetClaw to summarize work using the tickets and connected sources you can access.                                                                |
| **Stay ahead of work**   | Receive a morning briefing and create reminders. JanetClaw can also flag messages that still need a response.                                          |
| **Run coding tasks**     | Ask JanetClaw to take a ticket from planning to a draft pull request with Claude Code.                                                                 |
| **Build team workflows** | Add a command for an on-demand report. You can schedule a recurring check or create a trigger for a specific event.                                    |

JanetClaw records its work in the **Activity** section. Ticket actions also appear in the conversation where the work started.

## Set up JanetClaw

### Before you start

You need:

* Organization admin access
* A Slack workspace you can connect
* Available JanetClaw credits or shared trial credits

New organizations can start with their shared signup credits without adding a card. If your organization is out of credits, an admin can buy credits from **Organization Settings → Billing**.

<Steps>
  <Step title="Open JanetClaw">
    Select **JanetClaw** in the sidebar. Only an organization admin can create the assistants.
  </Step>

  <Step title="Connect Slack">
    Select **Sign in with Slack** and authorize the JanetClaw app for your workspace.
  </Step>

  <Step title="Set up the team assistant">
    Select **Team assistant**. Janet creates the cloud pod and shows its progress. Setup usually takes a couple of minutes, and you can close the modal while it runs.
  </Step>

  <Step title="Configure your assistant">
    In **General**, choose the point of contact and timezone. Set the work hours and morning briefing next. You can also choose monitored inboxes and the background activity level.
  </Step>
</Steps>

To add customer support, open **Organization → Customer support** after the team assistant is live. Set up the assistant, then enroll each Slack Connect channel where it should respond.

## Customize how JanetClaw works

Use the **Configure** sections to shape its behavior:

* **Commands** run when someone invokes a custom slash command.
* **Schedules** run at a time or cadence you choose.
* **Triggers** run when a defined event happens.
* **Instructions** control tone and organization-specific guidance. You can also add knowledge base URLs.

You can add a ready-made workflow or write your own. JanetClaw stores these behaviors in its playbook, where you can disable or update them later.

## Connect other tools

Open **Integrations** to connect an available provider. Choose **Just me** for a personal connection. Admins can choose **Whole team** when a provider supports organization-wide access.

Personal connections stay private to the member who connected them. Team connections are available to the shared team assistant. The customer support assistant cannot use either type.

Email and calendar workflows require each member to connect their own Google account with **Just me** access.

## Manage usage

JanetClaw uses organization credits for direct requests and background work. Running cloud assistants also uses platform credits. In **General**, change **Activity level** to control how often JanetClaw wakes up for background checks.

Admins can review credit use in **Organization Settings → Usage**. Manage plans and add credits from **Organization Settings → Billing**.


# MCP Server
Source: https://docs.janet.ai/mcpserver

Connect AI agents to your organization

<div>
  <div>
    <div>
      <div>
        <span />

        <span />

        <span />
      </div>

      <span>claude — \~/projects/frontend</span>

      <div />
    </div>

    <div>
      <div>
        <span>›</span>
        <span>look at my tickets in "To Do" and make a plan for how I should prioritize and finish them</span>
      </div>

      <div>
        <div>
          <span />

          <span><strong>janet-ai - list\_tickets (MCP)</strong><span>(project\_key: "SW", status: "To Do", assignees: \["me"])</span></span>
        </div>

        <div>
          <span />

          <span><strong>janet-ai - list\_tickets (MCP)</strong><span>(project\_key: "SW", status: "To Do", assignees: \["me"])</span></span>
        </div>
      </div>

      <div>
        <span />

        <span>You have 4 tickets in To Do. Here's how I'd tackle them:</span>
      </div>

      <div>
        <span />

        <span>1. <strong>SW-84</strong> SSO token refresh — blocking other auth work, fix first</span>
      </div>

      <div>
        <span />

        <span>2. <strong>SW-71</strong> OAuth callback timeout — related to SSO, do right after</span>
      </div>

      <div>
        <span />

        <span>3. <strong>SW-63</strong> Session cookie fix — standalone, quick win</span>
      </div>

      <div>
        <span />

        <span>4. <strong>SW-58</strong> Safari redirect — lowest impact, last</span>
      </div>

      <div />

      <div>
        <span />

        <span>Want me to spawn agents to start working through these?</span>
      </div>

      <div>
        <span>›</span>

        <span />
      </div>
    </div>
  </div>
</div>

Give AI agents like Claude Code, Cursor, and Codex full access to your Janet AI workspace. Create & resolve tickets, manage sprints, and [more](#available-tools).

## Setup

<Tabs>
  <Tab title="Claude Code">
    Run this command in your terminal:

    ```bash theme={null}
    claude mcp add janet-ai --transport http https://mcp.janet.ai/mcp
    ```

    Then run `/mcp` in Claude Code and complete the OAuth flow to connect your Janet AI Organization.
  </Tab>

  <Tab title="Claude Desktop">
    Open **Settings → Connectors → Add custom connector** and enter the URL:

    ```
    https://mcp.janet.ai/mcp
    ```

    Complete the OAuth flow to connect your Janet AI organization.

    <Callout icon="circle-info">Remote MCP servers in Claude Desktop are configured through Settings → Connectors, not the `claude_desktop_config.json` file.</Callout>
  </Tab>

  <Tab title="Cursor">
    Go to **Cursor Settings → Tools & MCP** and click **New MCP Server**. This opens `mcp.json` — add the following:

    ```json theme={null}
    {
      "mcpServers": {
        "janet-ai": {
          "url": "https://mcp.janet.ai/mcp"
        }
      }
    }
    ```

    Save, then back in Cursor Settings click **Connect** next to janet-ai to authenticate and choose your organization.
  </Tab>

  <Tab title="VS Code">
    Create or edit `.vscode/mcp.json` in your workspace:

    ```json theme={null}
    {
      "servers": {
        "janet-ai": {
          "type": "http",
          "url": "https://mcp.janet.ai/mcp"
        }
      }
    }
    ```

    Open the Command Palette and run **MCP: List Servers**, then start the Janet AI server and complete the OAuth flow.
  </Tab>

  <Tab title="Windsurf">
    Open Windsurf Settings and search for **MCP**. Click **View raw config** to open `mcp_config.json`, then add:

    ```json theme={null}
    {
      "mcpServers": {
        "janet-ai": {
          "serverUrl": "https://mcp.janet.ai/mcp"
        }
      }
    }
    ```

    Save, restart Windsurf, and complete the OAuth flow on first use.
  </Tab>

  <Tab title="Codex">
    Run this command in your terminal:

    ```bash theme={null}
    codex mcp add janet-ai --url https://mcp.janet.ai/mcp
    ```

    Then run `codex mcp login janet-ai` and complete the OAuth flow to connect your workspace.
  </Tab>
</Tabs>

## What You Can Do

Once connected, just talk to your AI agent naturally:

| Use case              | Example prompt                                                    |
| --------------------- | ----------------------------------------------------------------- |
| **Find tickets**      | "Show me my assigned tickets in MAIN"                             |
| **Search**            | "Search for tickets about authentication"                         |
| **Create tickets**    | "Create a high-priority bug for the login redirect issue"         |
| **Schedule tickets**  | "Schedule a ticket for tomorrow at 9am to review the deployment"  |
| **Update tickets**    | "Move MAIN-452 to In Progress"                                    |
| **Manage sprints**    | "Add MAIN-100 and MAIN-101 to Sprint 3"                           |
| **Create objectives** | "Create an objective called Q2 Launch with high priority"         |
| **Manage objectives** | "Add MAIN-100 and MAIN-101 to the Q2 Launch objective"            |
| **Add comments**      | "Add a comment to MAIN-100 saying the fix is deployed"            |
| **Attach context**    | "Add this Slack thread / PR / email / doc to MAIN-123 as context" |
| **Break down work**   | "Create child tasks on MAIN-200 for each component"               |
| **Sort & organize**   | "Sort the To Do column by priority"                               |
| **Web search**        | "What are the best libraries for rate limiting in Node.js?"       |
| **Write docs**        | "Create a document called API Design with the proposed structure" |

### Available Tools

The MCP server exposes 40 tools that your AI agent discovers and uses automatically.

<Accordion title="Workspace">
  <ResponseField name="get_workspace_context">Get user info, organization, projects, statuses, and members.</ResponseField>
  <ResponseField name="get_platform_guidance">Get platform documentation and usage guidance.</ResponseField>
</Accordion>

<Accordion title="Tickets">
  <ResponseField name="list_tickets">List tickets with optional filters (status, priority, assignee, keyword, dates).</ResponseField>
  <ResponseField name="get_tickets">Get full ticket details including description, comments, and child tasks for one or more tickets.</ResponseField>
  <ResponseField name="create_tickets">Create one or more tickets in a single call (title, description, status, priority, assignees, labels, sprint, due date, scheduled activation).</ResponseField>
  <ResponseField name="update_tickets">Batch update ticket fields (status, priority, assignees, labels, due date).</ResponseField>
  <ResponseField name="delete_tickets">Soft-delete one or more tickets in a single call. Restorable.</ResponseField>
  <ResponseField name="restore_tickets">Restore one or more previously deleted tickets together with their child tasks.</ResponseField>
  <ResponseField name="move_ticket">Reposition a ticket: top, bottom, at:N, before/after, within kanban, sprint, or objective. Also supports column-wide `sort` and `reorder`.</ResponseField>
  <ResponseField name="search_tickets_semantic">Semantic search across tickets by meaning.</ResponseField>
</Accordion>

<Accordion title="Ticket Context">
  <ResponseField name="add_context_to_tickets">Attach context to one or more tickets in a single call. The `type` arg picks the source: `slack` (permalink or manual reporter+message), `discord` (permalink or manual username+message), `email` (sender, subject, body), `pull_request` (URL), `web_link` (URL), or `document` (Janet AI doc by UUID or exact title — idempotent).</ResponseField>
  <ResponseField name="list_ticket_context">List every context item on a ticket (Slack/Discord/email messages, PRs, web links, linked Janet docs, meetings, Google Docs) with its id + short description. Call this before `remove_context_from_ticket`.</ResponseField>
  <ResponseField name="remove_context_from_ticket">Remove a context item from a ticket by id (id comes from `list_ticket_context`). Works on any context type.</ResponseField>
</Accordion>

<Accordion title="Child Tasks">
  <ResponseField name="list_child_tasks">List child tasks for a ticket.</ResponseField>
  <ResponseField name="create_child_tasks">Create one or more child tasks on a ticket in a single call.</ResponseField>
  <ResponseField name="update_child_tasks">Batch update child task title, status, priority, or assignee.</ResponseField>
  <ResponseField name="delete_child_tasks">Delete one or more child tasks in a single call.</ResponseField>
</Accordion>

<Accordion title="Comments">
  <ResponseField name="list_comments">List comments on a ticket.</ResponseField>
  <ResponseField name="add_comments">Add one or more comments to one or more tickets in a single call.</ResponseField>
  <ResponseField name="edit_comments">Batch edit existing comments. Edit history is preserved (the original row is deactivated, a new row inserted with the original `created_at`).</ResponseField>
  <ResponseField name="delete_comments">Delete one or more comments in a single call.</ResponseField>
</Accordion>

<Accordion title="Sprints">
  <ResponseField name="list_sprints">List sprints with status, dates, and ticket counts.</ResponseField>
  <ResponseField name="create_sprint">Create a new sprint.</ResponseField>
  <ResponseField name="update_sprint">Update a sprint's name, dates, status, or description.</ResponseField>
  <ResponseField name="add_sprint_tickets">Add tickets to a sprint.</ResponseField>
  <ResponseField name="remove_sprint_tickets">Remove tickets from a sprint.</ResponseField>
  <ResponseField name="list_sprint_tickets">List tickets in a sprint grouped by status.</ResponseField>
</Accordion>

<Accordion title="Objectives">
  <ResponseField name="list_objectives">List objectives with status, priority, and ticket counts.</ResponseField>
  <ResponseField name="create_objective">Create a new objective.</ResponseField>
  <ResponseField name="update_objective">Update an objective's name, status, priority, or assignees.</ResponseField>
  <ResponseField name="delete_objective">Delete an objective.</ResponseField>
  <ResponseField name="add_objective_tickets">Add tickets to an objective.</ResponseField>
  <ResponseField name="remove_objective_tickets">Remove tickets from an objective.</ResponseField>
  <ResponseField name="list_objective_tickets">List tickets in an objective grouped by status.</ResponseField>
</Accordion>

<Accordion title="Documents">
  <ResponseField name="list_documents">List documents in the workspace.</ResponseField>
  <ResponseField name="get_document">Get a document's full content.</ResponseField>
  <ResponseField name="create_document">Create a document with title and markdown content.</ResponseField>
  <ResponseField name="update_document">Update a document's title or content.</ResponseField>
</Accordion>

<Accordion title="Web">
  <ResponseField name="web_search">Search the web for current information.</ResponseField>
</Accordion>

<Accordion title="JanetClaw">
  <ResponseField name="post_janetclaw_activity">Post an activity message to the user's JanetClaw feed for distinct JanetClaw actions (creating a ticket from email, adding context, moving tickets when a PR merges, etc.). Pass `ticket_key` — click-through URLs resolve automatically.</ResponseField>
</Accordion>

## Activity Log

Every MCP tool call is logged and visible in the **MCP page** → **Usage tab** in your dashboard. Organization admins see all members' calls; members see only their own.

## Troubleshooting

### Cannot connect / authentication errors

If your client fails to connect, try:

1. **Clear existing auth** — In your client, remove and re-add the MCP server to trigger a fresh OAuth flow.
2. **Check your organization** — During sign-in, make sure you select the correct organization.
3. **Restart your client** — Some clients need a full restart after the OAuth flow completes.

## FAQ

<AccordionGroup>
  <Accordion title="What are the rate limits?">
    The MCP server enforces per-user rate limits. If you hit a `429 Too Many Requests` error, wait a minute before retrying. Typical limits are 200 requests/minute and 5,000 requests/hour per user.

    If you consistently hit rate limits, contact [support@janet.ai](mailto:support@janet.ai).
  </Accordion>

  <Accordion title="Is there a Janet CLI tool?">
    [`mcporter`](https://github.com/steipete/mcporter) lets you call MCP tools directly as CLI commands — no agent required.

    First, install it globally:

    ```bash theme={null}
    npm install mcporter
    ```

    Authenticate once locally:

    ```bash theme={null}
    mcporter auth https://mcp.janet.ai/mcp
    ```

    Then call any tool directly from the command line:

    ```bash theme={null}
    mcporter call janet-ai.list_tickets --project_key MAIN --status "To Do"
    ```
  </Accordion>

  <Accordion title="How do I use CLI commands in my cloud-hosted scripts?">
    First, install it globally and authenticate on your local machine:

    ```bash theme={null}
    npm install mcporter
    mcporter auth https://mcp.janet.ai/mcp
    ```

    Credentials are stored in `~/.mcporter/credentials.json` — copy that file's contents as a secret or environment variable in your cloud environment so scripts can run without an interactive OAuth flow.

    For example, a Python script that creates a ticket:

    ```python theme={null}
    import json
    import subprocess

    subprocess.run([
        "mcporter", "call", "janet-ai.create_tickets",
        "--tickets", json.dumps([{
            "title": "Nightly health check failed",
            "project_key": "MAIN",
            "priority": "High",
        }]),
    ])
    ```
  </Accordion>

  <Accordion title="My agent doesn't support the OAuth PKCE flow — how do I connect?">
    Some agent runtimes support HTTP-based MCP servers but don't implement the OAuth PKCE flow required by Janet AI (e.g. [OpenClaw](https://openclaw.ai)). You can proxy through [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) to handle auth transparently.

    First, install it:

    ```bash theme={null}
    npm install -g mcp-remote
    ```

    Then trigger the OAuth flow in your terminal:

    ```bash theme={null}
    mcp-remote https://mcp.janet.ai/mcp
    ```

    Then configure your agent to use it:

    ```json theme={null}
    {
      "mcpServers": {
        "janet-ai": {
          "command": "mcp-remote",
          "args": ["https://mcp.janet.ai/mcp"]
        }
      }
    }
    ```

    `mcp-remote` runs locally, performs the PKCE handshake with `https://mcp.janet.ai/mcp` on your behalf, and exposes the server over stdio to your agent. This works with any client that supports stdio-based MCP servers.
  </Accordion>
</AccordionGroup>


# Quickstart
Source: https://docs.janet.ai/quickstart



## Create an Organization

Your organization is the top-level container for all projects and team members. Open the **organization selector** in the sidebar and click **Create Organization**.

<div>
  <div>
    <div>
      <div>
        <div>
          <div>
            <span>A</span>
            <span>Acme Inc</span>

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>
              <span>A</span>
              <span>Acme Inc</span>
            </div>

            <div>
              <span>S</span>
              <span>Side Project</span>
            </div>

            <div />

            <div>
              <svg>
                <path />

                <path />
              </svg>

              <span>Create Organization</span>
            </div>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <rect />

              <rect />

              <rect />

              <rect />
            </svg>

            <span>Dashboard</span>
          </div>

          <div>
            <svg>
              <path />
            </svg>

            <span>Projects</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>Documents</span>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            <span>Reports</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>MCP</span>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            <span>Integrations</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>Settings</span>
          </div>
        </div>
      </div>
    </div>

    <div>
      <div>
        <div>Acme Inc</div>
        <div>Organization Dashboard</div>
      </div>
    </div>
  </div>
</div>

## Create a Project

Projects organize tickets by product, team, or initiative. Navigate to **Projects** and click **Create**.

<div>
  <div>
    <div>
      <div>
        <div>
          <div>
            <span>A</span>
            <span>Acme Inc</span>

            <svg>
              <path />
            </svg>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <rect />

              <rect />

              <rect />

              <rect />
            </svg>

            <span>Dashboard</span>
          </div>

          <div>
            <svg>
              <path />
            </svg>

            <span>Projects</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>Documents</span>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            <span>Reports</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>MCP</span>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            <span>Integrations</span>
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            <span>Settings</span>
          </div>
        </div>
      </div>
    </div>

    <div>
      <div>
        <span>
          <svg>
            <path />

            <path />
          </svg>

          <span>Search</span>
          <span>⌘K</span>
        </span>

        <span>
          <svg>
            <path />

            <path />
          </svg>

          <span>Create</span>
        </span>
      </div>

      <div>
        <div>Projects</div>
        <div>Manage your Acme Inc projects</div>

        <div>
          <div>
            <span>Mobile App</span>
            <span>MOB</span>
          </div>

          <div>
            <span>Web App</span>
            <span>WEB</span>
          </div>

          <div>
            <span>GTM</span>
            <span>GTM</span>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## Create Tickets

Click **+** from the project header to open the create ticket modal. Fill in the details and Janet takes it from there — auto-tagging, suggesting assignees, and evaluating quality.

<div>
  <div>
    <div>
      <div>
        <span>Create Ticket</span>

        <div>
          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span />

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span />

          <span>
            <img alt="" />
          </span>
        </div>
      </div>

      <div>
        <div>
          <span>
            <img alt="" />

            <span>Will Barthell</span>
            <span>×</span>
          </span>

          <span>payments<span>×</span></span>
          <span>checkout<span>×</span></span>
        </div>

        <div>Users getting 500 errors on checkout with discount codes</div>

        <div>
          <div><p>Multiple reports of 500 errors when applying discount codes over \$50 at checkout. Appears to affect coupon codes with percentage-based discounts. Reproduced on both web and mobile clients.</p></div>
        </div>
      </div>

      <div>
        <div />

        <div>
          <span><svg><path /><path /><path /><path /><path /></svg> Autofill</span>
          <span>Create</span>
        </div>
      </div>
    </div>
  </div>
</div>

## Next Steps

<CardGroup>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Create, update, and search your tickets directly from Slack
  </Card>

  <Card title="GitHub" icon="github" href="/integrations/github">
    Sync pull requests and issues with your Janet AI tickets
  </Card>

  <Card title="MCP Server" icon="robot" href="/mcp">
    Connect Claude Code, Cursor, and other AI agents to your workspace
  </Card>
</CardGroup>


# Auto-Fill
Source: https://docs.janet.ai/ticket-features/auto-fill

Enrich ticket details from project context

<div>
  <div>
    <div>
      <div>
        <span>Create Ticket</span>

        <div>
          <div>
            <div>
              <div>
                <span>
                  <img alt="" />
                </span>

                <span>
                  <img alt="" />
                </span>

                <span>
                  <img alt="" />
                </span>
              </div>
            </div>

            <div>
              <div>
                <span>
                  <img alt="" />
                </span>

                <span>
                  <img alt="" />
                </span>

                <span>
                  <img alt="" />
                </span>
              </div>
            </div>
          </div>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span />

          <span>
            <img alt="" />
          </span>

          <span>
            <img alt="" />
          </span>

          <span />

          <span>
            <img alt="" />
          </span>
        </div>
      </div>

      <div>
        <div>
          <div>
            <div>
              <div />
            </div>

            <div>
              <div>
                <span>
                  <img alt="" />

                  <span>Will Barthell</span>
                  <span>×</span>
                </span>

                <span>mobile<span>×</span></span>
                <span>auth<span>×</span></span>

                <span>
                  <img alt="" />

                  Sprint 12
                  <span>×</span>
                </span>

                <span>
                  <img alt="" />

                  Mobile Bugs
                  <span>×</span>
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>Users can't reset their password from the mobile app</div>

        <div>
          <div>
            <div><div><span>Add a description...</span></div></div>
            <div><div><div>Steps to reproduce</div><p>1. Open the mobile app and tap "Forgot password"<br />2. Enter email and submit<br />3. The reset email is never received</p><div>Expected behavior</div><p>User receives a password reset link within 30 seconds.</p></div></div>
          </div>
        </div>
      </div>

      <div>
        <div />

        <div>
          <div>
            <span><svg><path /></svg> Autofilling...</span>
          </div>

          <span>Create</span>
        </div>
      </div>
    </div>
  </div>
</div>

## How it works

Type a title in the create ticket modal and click **Autofill** in the footer. The agent analyzes your title against existing tickets in the project and fills in the description, priority, issue type, labels, and assignee. Adjust anything that looks off, then create the ticket.


# Auto-Tagging
Source: https://docs.janet.ai/ticket-features/auto-tagging

Tag tickets when they're created or updated

<div>
  <div>
    <div>
      <div>Auto-Tagging</div>
      <p>Configure tags that will be automatically added by Janet AI every time a ticket is created or updated. This will not overwrite tags you manually add.</p>
    </div>

    <div>
      <div>
        <span>
          <svg>
            <path />
          </svg>

          Add
        </span>
      </div>

      <div>
        <div>
          <div>
            <div>Frontend</div>
            <div>Apply to tickets about UI components, styling, or browser issues</div>
          </div>

          <span>
            <svg>
              <path />

              <path />

              <path />
            </svg>
          </span>
        </div>

        <div>
          <div>
            <div>Performance</div>
            <div>Apply when the ticket mentions slow loading, latency, or optimization</div>
          </div>

          <span>
            <svg>
              <path />

              <path />

              <path />
            </svg>
          </span>
        </div>

        <div>
          <div>
            <div>Acme Corp</div>
            <div>Apply to tickets reported by or affecting the Acme Corp account</div>
          </div>

          <span>
            <svg>
              <path />

              <path />

              <path />
            </svg>
          </span>
        </div>
      </div>
    </div>
  </div>
</div>

## How it works

You define tag names with a short description of when each should apply. Every time a ticket is created or updated, the content is analyzed and matching tags are added automatically. Tags you add manually are never overwritten.

## Set-up

Click the **Gear** icon in the header of your **Project Board** to access **Project Settings**, select the **Configure** tab, then add tags.

<div>
  <div>
    <div>
      <div>
        <div>PROJECT SETTINGS</div>

        <div>
          <div>
            <svg>
              <path />

              <path />

              <path />

              <path />
            </svg>

            Members
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            Configure

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Kanban Columns</div>
            <div>Resolved Filter</div>
            <div>Ticket Style</div>
            <div>Auto-Tagging</div>
            <div>Ticket Rubric</div>
            <div>Recurring Actions</div>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            Danger Zone
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>A</div>

          <div>
            <span>
              <span>Acme <span>Project</span></span>
              <code>ACME</code>
            </span>

            <div>
              <svg>
                <rect />

                <path />
              </svg>

              <span><span>Created </span>Jan 15, 2025</span>
            </div>
          </div>
        </div>

        <div>
          <div>Auto-Tagging</div>
          <div>Configure tags that will be automatically added every time a ticket is created or updated.</div>

          <div>
            <div>
              <div>
                <div>Frontend</div>
                <div>Apply to tickets about UI components, styling, or browser issues</div>
              </div>

              <span>
                <svg>
                  <path />

                  <path />

                  <path />
                </svg>
              </span>
            </div>

            <div>
              <div>
                <div>Performance</div>
                <div>Apply when the ticket mentions slow loading, latency, or optimization</div>
              </div>

              <span>
                <svg>
                  <path />

                  <path />

                  <path />
                </svg>
              </span>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>


# Code Runs
Source: https://docs.janet.ai/ticket-features/code-runs

Run Claude Code on tickets in Anthropic-hosted containers

<div>
  <div>
    <div>
      <div>
        <span>
          <span>
            <svg>
              <path />
            </svg>
          </span>

          <span>ACME-42</span>
        </span>
      </div>

      <div>
        <span>
          <span>
            <img alt="" />
          </span>

          <span>acme-backend</span>
        </span>

        <span>
          <svg>
            <path />

            <path />

            <path />

            <path />
          </svg>

          <span>main</span>
        </span>
      </div>
    </div>

    <div>
      <p>Add retry logic to the webhook handler and cover the 429 path in tests.</p>
    </div>

    <div>
      <div>
        <span>
          <span>Edits</span>

          <svg>
            <polyline />
          </svg>
        </span>

        <span>
          <img alt="" />

          <span>Sonnet 4.6</span>

          <svg>
            <polyline />
          </svg>
        </span>
      </div>

      <span>
        <svg>
          <path />
        </svg>
      </span>
    </div>
  </div>
</div>

**Code Runs** send tickets to **Claude Code** inside [Anthropic Managed Agents](https://platform.claude.com/docs/en/managed-agents/overview) cloud containers. Each ticket gets a **conversation** at `/code-runs/{ticketKey}` where you stream turns, review plans, accept edits, and open **draft pull requests** on connected GitHub repos.

One ticket maps to one org-wide chat thread. Repos you select are cloned into a **shared workspace** (up to six per run) so Claude can work across them; when you use **Edits** with **Auto open draft PR** enabled, Janet opens draft PRs via the **GitHub App** for repos that have changes.

## Prerequisite

* **GitHub:** Connect the GitHub App, enable repositories for your organization, and link repos to projects when you want them pre-selected. See [GitHub integration](/integrations/github).

## Start a code run

Submit from any of these entry points; Janet stashes your repo, model, mode, and instructions, then opens the ticket conversation.

| Entry point             | What happens                                                                                                        |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Code Runs** (sidebar) | Home composer — pick or create a ticket, configure repos and mode, submit. Subtitle: *Send tickets to Claude Code*. |
| **Ticket details**      | **Create PR** in the Code Runs section opens **Quick Input** in code-run mode (same composer).                      |
| **Edit ticket modal**   | Footer **Send to Claude Code** opens Quick Input in code-run mode (Kanban: right-click a card → edit).              |

Use **New Code Run** in the Code Runs sidebar (**⇧N**) to return to the home composer.

## Composer options

The composer appears on the Code Runs home page, in Quick Input code-run mode, and when starting from a ticket. On the home page it uses the same large rounded **chat-style** input as Janet Chat: **Add ticket** and **Add repos** pills on top, instructions in the middle, and **Edits** / model controls plus a send arrow in the footer.

* **Ticket:** On the home page, use the dashed **Add ticket** pill (or create a ticket from the picker). When you start from a ticket surface, the ticket is already set.
* **Repositories:** **Add repos** to choose one or more targets and set each **branch** (draft PR base). Repos linked to the ticket’s project are pre-selected when possible. At most **six** repositories per run.
* **Model:** **Sonnet 4.6** (default) or **Opus 4.8**. Your default can be set under **Account → AI settings** (coding model).
* **Mode:**
  * **Ask** — Read-only Q\&A about the code; no edits and no plan artifact.
  * **Edits** — Claude may change files in the container. Open the mode menu to toggle **Auto open draft PR** (off by default). When enabled, Janet opens draft PR(s) after a successful implement turn when there are changes.
  * **Plan** — Exploration and a written implementation plan only; plan turns do not edit repos or open PRs.
* **Instructions:** Optional text up to **8000** characters. Before you pick a ticket, the field shows *Add additional instructions...*; after a ticket is selected, *Add instructions for Claude Code (optional)*.

## Run statuses

| Status          | Meaning                                                                                                                     |
| --------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Queued**      | Turn accepted, waiting to start (legacy rows).                                                                              |
| **Running**     | Claude is actively working.                                                                                                 |
| **Needs input** | Waiting for your answer in the chat.                                                                                        |
| **Failed**      | Turn or setup failed; error details appear in the thread. Retry from **Create PR** / **Send to Claude Code** on the ticket. |
| **PR opened**   | A draft PR link is available.                                                                                               |
| **Idle**        | Last turn finished with no PR; the session stays open for more messages.                                                    |


# Recurring Actions
Source: https://docs.janet.ai/ticket-features/recurring-actions

Schedule recurring ticket creation or Janet Agent prompts

<div>
  <div>
    <div>
      <div>
        <span>Automations</span>
        <span>Logs</span>
      </div>

      <span>
        <svg>
          <path />
        </svg>

        Add
      </span>
    </div>

    <div>
      <div>
        <div>
          <div>
            <div>
              <span>Weekly DB Audit</span>
              <span>Create Ticket</span>
            </div>

            <div>
              <span>
                <svg>
                  <path />

                  <path />
                </svg>

                Fri at 9:00 AM PT
              </span>
            </div>

            <div>Created by [alice@acme.com](mailto:alice@acme.com)</div>
          </div>

          <div>
            <span>
              <svg>
                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <div>
              <span />
            </div>
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>
            <div>
              <span>Blocked Ticket Followup</span>
              <span>Agent Prompt</span>
            </div>

            <div>
              <span>
                <svg>
                  <path />

                  <path />
                </svg>

                Mon, Wed, Fri at 10:00 AM PT
              </span>
            </div>

            <div>Created by [bob@acme.com](mailto:bob@acme.com)</div>
          </div>

          <div>
            <span>
              <svg>
                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <div>
              <span />
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

Create tickets or run agent prompts daily, weekly, or on a custom cadence.

## Action types

Each recurring action is one of two types:

<AccordionGroup>
  <Accordion title="Create Ticket">
    Deterministic ticket creation with pre-configured fields. Every time the schedule fires, a new ticket is added to the project with the title, description, status, priority, type, assignees, and tags you specify.

    Useful for repeatable tasks your team does on a cadence: weekly audits, recurring standups, monthly reviews.
  </Accordion>

  <Accordion title="Agent Prompt">
    A freeform prompt that the agent executes at the scheduled time. It has full access to your project context: it can search tickets, create or update them, leave comments, and [more](/agent).

    Useful for tasks that require reasoning: following up on blocked tickets, generating summary reports, or triaging unassigned work.
  </Accordion>
</AccordionGroup>

## Set-up

Click the **Gear** icon in the header of your **Project Board** to access **Project Settings**, select the **Configure** tab, then select **Recurring Actions**.

<div>
  <div>
    <div>
      <div>
        <div>PROJECT SETTINGS</div>

        <div>
          <div>
            <svg>
              <path />

              <path />

              <path />

              <path />
            </svg>

            Members
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            Configure

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Kanban Columns</div>
            <div>Resolved Filter</div>
            <div>Ticket Style</div>
            <div>Auto-Tagging</div>
            <div>Ticket Rubric</div>
            <div>Recurring Actions</div>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            Danger Zone
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>A</div>

          <div>
            <span>
              <span>Acme <span>Project</span></span>
              <code>ACME</code>
            </span>

            <div>
              <svg>
                <rect />

                <path />
              </svg>

              <span><span>Created </span>Jan 15, 2025</span>
            </div>
          </div>
        </div>

        <div>
          <div>Recurring Actions</div>
          <div>Schedule recurring tickets or agent tasks to run automatically on a cadence.</div>

          <div>
            <div>
              <div>
                <div>
                  <span>Weekly DB Audit</span>
                  <span>Create Ticket</span>
                </div>

                <div />
              </div>

              <div>
                <svg>
                  <path />

                  <path />
                </svg>

                <span>Every Friday at 9:00 AM (PT)</span>
              </div>
            </div>

            <div>
              <div>
                <div>
                  <span>Triage unassigned tickets</span>
                  <span>Agent Prompt</span>
                </div>

                <div />
              </div>

              <div>
                <svg>
                  <path />

                  <path />
                </svg>

                <span>Every Mon, Wed, Fri at 8:00 AM (PT)</span>
              </div>
            </div>

            <div>
              <div>
                <div>
                  <span>Sprint retro ticket</span>
                  <span>Create Ticket</span>
                </div>

                <div />
              </div>

              <div>
                <svg>
                  <path />

                  <path />
                </svg>

                <span>Every Friday at 4:00 PM (PT)</span>
              </div>
            </div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

## Creating a recurring action

<div>
  <div>
    <div>
      <div>New Automation</div>

      <div>
        <span>Name</span>
        <div>Weekly DB Audit</div>
      </div>

      <div>
        <span>Action</span>

        <div>
          <span>Create Ticket</span>
          <span>Agent Prompt</span>
        </div>
      </div>

      <div>
        <span>Schedule</span>

        <div>
          <span>Su</span>
          <span>Mo</span>
          <span>Tu</span>
          <span>We</span>
          <span>Th</span>
          <span>Fr</span>
          <span>Sa</span>
        </div>

        <div>
          <div>
            <span>Time</span>

            <div>
              <span>09:00 AM</span>

              <svg>
                <path />
              </svg>
            </div>
          </div>

          <div>
            <span>Timezone</span>

            <div>
              <span>Pacific (PT)</span>

              <svg>
                <path />
              </svg>
            </div>
          </div>
        </div>
      </div>

      <div />

      <div>
        <span>Ticket Title <span>\*</span></span>
        <div>Audit database logs</div>
      </div>

      <div>
        <span>Description</span>
        <div>Review slow queries and check for anomalies in the past week's logs.</div>
      </div>

      <div>
        <div>
          <span>Status</span>

          <div>
            <span>To Do</span>

            <svg>
              <path />
            </svg>
          </div>
        </div>

        <div>
          <span>Priority</span>

          <div>
            <span>Medium</span>

            <svg>
              <path />
            </svg>
          </div>
        </div>

        <div>
          <span>Type</span>

          <div>
            <span>Task</span>

            <svg>
              <path />
            </svg>
          </div>
        </div>

        <div>
          <span>Due Date</span>

          <div>
            <span>None</span>

            <svg>
              <path />
            </svg>
          </div>
        </div>
      </div>

      <div>
        <span>Create Automation</span>
        <span>Cancel</span>
      </div>
    </div>
  </div>
</div>

Select the action type, pick which days and time it should run, and fill in the details.

## Managing automations

Each rule has a toggle to enable or disable it, a play button to trigger it immediately, and edit/delete controls. The **Logs** tab shows a full history of every run (status, timing, and for agent prompts, the full tool call chain and response).

Only project admins can create or modify automations. All members can view them.

## Examples

<Tabs>
  <Tab title="Create Ticket">
    **Weekly database audit** — every Friday at 9 AM

    **Sprint retro ticket** — every Friday at 4 PM

    **Daily standup prep** — weekdays at 8:30 AM
  </Tab>

  <Tab title="Agent Prompt">
    **Follow up on blocked tickets** — Mon/Wed/Fri at 10 AM

    **Triage unassigned bugs** — daily at 8 AM

    **Generate weekly summary** — every Friday at 5 PM
  </Tab>
</Tabs>


# Scheduled Tickets
Source: https://docs.janet.ai/ticket-features/scheduled-tickets

Create tickets that activate in your project at a future date

<div>
  <div>
    <div>
      <div>
        <span>‹</span>
        <span>April 2026</span>
        <span>›</span>
      </div>

      <div>
        <span>Su</span><span>Mo</span><span>Tu</span><span>We</span><span>Th</span><span>Fr</span><span>Sa</span>
      </div>

      <div>
        <span /><span /><span /><span>1</span><span>2</span><span>3</span><span>4</span>
        <span>5</span><span>6</span><span>7</span><span>8</span><span>9</span><span>10</span><span>11</span>
        <span>12</span><span>13</span><span>14</span><span>15</span><span>16</span><span>17</span><span>18</span>
        <span>19</span><span>20</span><span>21</span><span>22</span><span>23</span><span>24</span><span>25</span>
        <span>26</span><span>27</span><span>28</span><span>29</span><span>30</span><span /><span />
      </div>

      <div>
        <span>Tomorrow 9am</span>
        <span>Monday 9am</span>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />
        </svg>

        Schedule

        <svg>
          <path />
        </svg>
      </span>

      <span>
        <svg>
          <path />

          <path />

          <path />
        </svg>

        Autofill with Janet
      </span>

      <div>
        <span>Cancel</span>
        <span>Create</span>
      </div>
    </div>
  </div>
</div>

## How it works

When creating a ticket, click **Schedule** in the modal footer and pick a date and time. The ticket stays invisible to everyone until the activation time arrives. You can toggle notifications via inbox, email, or SMS when it activates via **Account -> Notifications**.

## Viewing scheduled tickets

Click **Scheduled** in the **Project Page** header to see all pending tickets.

<div>
  <div>
    <div>
      <span>
        <svg>
          <path />

          <path />
        </svg>
      </span>

      <span>Scheduled Tickets</span>
      <span>4</span>

      <span>
        <svg>
          <path />

          <path />
        </svg>
      </span>
    </div>

    <div>
      <div>
        <span>Backlog</span>
        <span>2</span>
      </div>

      <div>
        <div>
          <svg>
            <rect />

            <rect />

            <rect />
          </svg>

          <span>PRJ-42</span>
        </div>

        <span>Audit Q1 security dependencies</span>

        <div>
          <img alt="" />

          <span>Apr 3, 9:00 AM</span>

          <div>
            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>

      <div>
        <div>
          <svg>
            <rect />

            <rect />
          </svg>

          <span>PRJ-51</span>
        </div>

        <span>Write onboarding guide for new engineers</span>

        <div>
          <img alt="" />

          <span>Apr 7, 9:00 AM</span>
        </div>
      </div>

      <div>
        <span>In Progress</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <svg>
            <rect />

            <rect />

            <rect />

            <rect />
          </svg>

          <span>PRJ-38</span>
        </div>

        <span>Deploy payment service hotfix to staging</span>

        <div>
          <img alt="" />

          <span>Mar 31, 2:00 PM</span>
        </div>
      </div>

      <div>
        <span>Review</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <svg>
            <rect />

            <rect />

            <rect />
          </svg>

          <span>PRJ-45</span>
        </div>

        <span>Follow up on design review feedback</span>

        <div>
          <img alt="" />

          <span>Apr 4, 10:00 AM</span>
        </div>
      </div>
    </div>
  </div>
</div>

Hover any row to **activate now** (skips the timer and places it on the board immediately) or **delete** (cancels it permanently). Click a row to edit the ticket or reschedule it to a different time.


# Ticket Evaluation
Source: https://docs.janet.ai/ticket-features/ticket-evaluation

Set custom ticket quality requirements

<div>
  <div>
    <div />

    <div>
      <div>Properties</div>

      <div>
        <div>
          <span>Issue Type</span>

          <div>
            <span>
              <span>
                <svg>
                  <path />
                </svg>
              </span>

              Bug
            </span>
          </div>
        </div>

        <div>
          <span>Status</span>

          <div>
            <span>
              <span />

              In Progress
            </span>
          </div>
        </div>

        <div>
          <span>Priority</span>

          <div>
            <span>
              <svg>
                <rect />

                <rect />

                <rect />
              </svg>

              High
            </span>
          </div>
        </div>
      </div>
    </div>

    <div />

    <div>
      <div>AI Insights</div>

      <div>
        <div>
          <span>Ticket Evaluation</span>

          <div>
            <span>
              Fail

              <svg>
                <path />

                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>

      <div>
        <div>Ticket Rubric Failed</div>

        <div>
          Missing steps to reproduce. The rubric requires bug tickets to include explicit reproduction steps in the description.
        </div>
      </div>
    </div>
  </div>
</div>

## How it works

Define quality standards for tickets with natural language. Each ticket is evaluated against your requirements and results are displayed on the ticket page.

## Set-up

Click the **Gear** icon in the header of your **Project Board** to access **Project Settings**, select the **Configure** tab, then add a **Ticket Rubric**.

<div>
  <div>
    <div>
      <div>
        <div>PROJECT SETTINGS</div>

        <div>
          <div>
            <svg>
              <path />

              <path />

              <path />

              <path />
            </svg>

            Members
          </div>

          <div>
            <svg>
              <path />

              <path />
            </svg>

            Configure

            <svg>
              <path />
            </svg>
          </div>

          <div>
            <div>Kanban Columns</div>
            <div>Resolved Filter</div>
            <div>Ticket Style</div>
            <div>Auto-Tagging</div>
            <div>Ticket Rubric</div>
            <div>Recurring Actions</div>
          </div>

          <div>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            Danger Zone
          </div>
        </div>
      </div>

      <div>
        <div>
          <div>A</div>

          <div>
            <span>
              <span>Acme <span>Project</span></span>
              <code>ACME</code>
            </span>

            <div>
              <svg>
                <rect />

                <path />
              </svg>

              <span><span>Created </span>Jan 15, 2025</span>
            </div>
          </div>
        </div>

        <div>
          <div>Ticket Rubric</div>
          <div>Define quality standards. Janet AI will evaluate each ticket against this rubric and show results on the ticket page.</div>

          <div>
            <div>96/1000 characters</div>
            <div>Tickets must always have a description. If the ticket describes a bug, the description must explicitly include steps to reproduce.</div>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>


# Views
Source: https://docs.janet.ai/views/dashboard

Customizable dashboards built from widgets

A **view** is a board of draggable, resizable widgets showing live workspace data. Create as many as you need, switch between them with tabs, and share them with your team.

<div>
  <div>
    <div>
      <div>
        <div>
          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>

          <span>Tickets</span>
        </div>

        <div><span /><span>MOB-42</span><span>Auth token refresh loop</span><span /></div>
        <div><span /><span>MOB-38</span><span>Push notification settings</span><span /></div>
        <div><span /><span>MOB-51</span><span>Onboarding empty states</span><span /></div>
        <div><span /><span>MOB-29</span><span>CSV export timeout</span><span /></div>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <path />

              <path />

              <path />
            </svg>
          </span>

          <span>Workload by owner</span>
        </div>

        <div>
          <div />

          <div>
            <div><span /><span>Will</span><span>9 open</span></div>
            <div><span /><span>Adhit</span><span>6 open</span></div>
            <div><span /><span>Maya</span><span>3 open</span></div>
          </div>
        </div>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>

          <span>Metrics</span>
        </div>

        <div>
          <div><span>24</span><div><div /></div><span>Open</span></div>
          <div><span>9</span><div><div /></div><span>In prog</span></div>
          <div><span>17</span><div><div /></div><span>Done</span></div>
          <div><span>3</span><div><div /></div><span>Overdue</span></div>
        </div>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <path />

              <path />
            </svg>
          </span>

          <span>Sprints</span>
        </div>

        <div><div><span>Sprint 14</span></div><span>Jun 16 – Jun 30 · 12 tickets</span></div>
        <div><div><span>Sprint 15</span></div><span>Jun 30 – Jul 14 · 8 tickets</span></div>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <rect />

              <path />
            </svg>
          </span>

          <span>Ticket activity</span>
        </div>

        <div>
          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />

          <span />
        </div>

        <div><span>Less</span><span /><span /><span /><span /><span /><span>More</span></div>
      </div>
    </div>
  </div>
</div>

## Start from a template

An empty view offers preset layouts. Pick a template below to preview it, then **Use template** builds the board instantly.

<input type="radio" name="vt" />

<input type="radio" name="vt" />

<input type="radio" name="vt" />

<input type="radio" name="vt" />

<input type="radio" name="vt" />

<input type="radio" name="vt" />

<div>
  <div>
    <label>My View</label>
    <label>Team View</label>
    <label>Project View</label>
    <label>Organization View</label>
    <label>Sprint View</label>
    <label>Triage View</label>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Assigned to me</span></div>

            <div>
              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>My open tickets</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Blocking me</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>My calendar</span></div>

            <div>
              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Scratchpad</span></div>

            <div>
              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />
        </svg>
      </span>

      <div><span>My View</span><span>Everything assigned to you and what needs your attention today.</span></div>
      <span>Use template</span>
    </div>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Team</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Tickets</span></div>

            <div>
              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Ticket activity</span></div>

            <div>
              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Objectives</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Tickets by assignee</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Workload by status</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />

          <path />

          <path />
        </svg>
      </span>

      <div><span>Team View</span><span>See how work is spread across your team and who's loaded up.</span></div>
      <span>Use template</span>
    </div>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Board</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Project health</span></div>

            <div>
              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Team</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Sprint time range</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Objectives</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Meeting notes</span></div>

            <div>
              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <rect />

          <rect />

          <rect />

          <rect />
        </svg>
      </span>

      <div><span>Project View</span><span>Keep tabs on a single project, from its board to its sprints.</span></div>
      <span>Choose project</span>
    </div>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Metrics</span></div>

            <div>
              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Tickets by status</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Projects</span></div>

            <div>
              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>

              <span>
                <span />

                <span />
              </span>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Objectives</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>People</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />

                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Signals & risks</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Hottest tickets</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />

          <path />

          <path />
        </svg>
      </span>

      <div><span>Organization View</span><span>A high-level read on how the whole organization is doing.</span></div>
      <span>Use template</span>
    </div>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Sprints</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Sprint board</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Metrics</span></div>

            <div>
              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>

              <div>
                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Sprint load</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Blockers</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Timeline</span></div>

            <div>
              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />

              <span />
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />
        </svg>
      </span>

      <div><span>Sprint View</span><span>Follow a sprint's progress and see what's left to ship.</span></div>
      <span>Choose sprint</span>
    </div>
  </div>

  <div>
    <div>
      <div />

      <div>
        <div>
          <div>
            <div><span>Overdue</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Blocked</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Recently updated</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Load by assignee</span></div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>

              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>
        </div>

        <div>
          <div>
            <div><span>Tickets by status</span></div>

            <div>
              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>

              <div>
                <span />

                <span>
                  <span />
                </span>
              </div>
            </div>
          </div>
        </div>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />

          <path />
        </svg>
      </span>

      <div><span>Triage View</span><span>Catch what's overdue or slipping before it falls through the cracks.</span></div>
      <span>Use template</span>
    </div>
  </div>
</div>

**Project View** and **Sprint View** ask which project or sprint to build around. A templated view behaves like any other afterward.

## Add and arrange widgets

<Steps>
  <Step title="Add">
    Click **Add widget** and pick from the menu.
  </Step>

  <Step title="Move">
    Drag a widget by the grip in its header.
  </Step>

  <Step title="Resize">
    Drag any edge or corner.
  </Step>

  <Step title="Remove">
    Right click the widget and choose **Remove**.
  </Step>
</Steps>

Right click a widget to configure it -- title, filters, project, time range, and more. Options vary by widget type.

## Widget catalog

| Category | Widgets                                                  |
| -------- | -------------------------------------------------------- |
| Work     | Tickets, High-context tickets, Signals, Activity heatmap |
| Planning | Objectives, Sprints, Calendar                            |
| Team     | Owners, Projects                                         |
| Content  | Summary card, Meeting notes, Documents                   |
| Advanced | Custom (AI)                                              |

The **Tickets** widget has four presentations -- list, board, status chart, and metrics -- switchable from its menu. **Custom (AI)** opens a chat where you describe the widget you want and Janet builds it.


# Kanban
Source: https://docs.janet.ai/views/kanban

Board view with columns for each status

<div>
  <div>
    <div>
      <div>
        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>Mobile App</span>
        <span>MOB</span>
      </div>

      <div>
        <div>
          <span><svg><rect /><rect /><rect /><rect /></svg><span>Kanban</span></span>
          <span><svg><path /><path /><path /></svg><span>List</span></span>
          <span><svg><path /></svg><span>Signals</span><span>New</span></span>
        </div>

        <span><svg><path /></svg><span>Create</span></span>

        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>
          <svg>
            <path />
          </svg>
        </span>
      </div>
    </div>

    <div>
      <div>
        <div><div><span>To Do</span><span>3</span></div><span><svg><path /><path /></svg></span></div>

        <div>
          <div><div><span>MOB-34</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Design onboarding flow for new users</span></div><div><img alt="" /><img alt="" /></div></div>
          <div><div><span>MOB-38</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Add push notification settings</span></div><div>          <img alt="" /></div></div>
          <div><div><span>MOB-41</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Localize date formats</span></div><div>          <img alt="" /></div></div>
        </div>
      </div>

      <div>
        <div><div><span>In Progress</span><span>2</span></div><span><svg><path /><path /></svg></span></div>

        <div>
          <div><div><span>MOB-29</span><span><svg><rect /><rect /><rect /><rect /></svg></span></div><div><span>Fix crash on deep-link redirect</span></div><div>          <img alt="" /></div></div>
          <div><div><span>MOB-31</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Implement biometric auth gate</span></div><div><img alt="" /><img alt="" /></div></div>
        </div>
      </div>

      <div>
        <div><div><span>In Review</span><span>2</span></div><span><svg><path /><path /></svg></span></div>

        <div>
          <div><div><span>MOB-26</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Refactor settings screen layout</span></div><div>          <img alt="" /></div></div>
          <div><div><span>MOB-33</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Update empty state illustrations</span></div><div><img alt="" /><img alt="" /></div></div>
        </div>
      </div>

      <div>
        <div><div><span>Done</span><span>2</span></div><span><svg><path /><path /></svg></span></div>

        <div>
          <div><div><span>MOB-22</span><span><svg><rect /><rect /><rect /></svg></span></div><div><span>Set up CI pipeline for staging</span></div><div>          <img alt="" /></div></div>
          <div><div><span>MOB-24</span><span><svg><rect /><rect /><rect /><rect /></svg></span></div><div><span>Patch token refresh race condition</span></div><div>          <img alt="" /></div></div>
        </div>
      </div>
    </div>
  </div>
</div>

Visualize your project as a board with columns for each status. Reorder tickets, drag and drop between columns to update their status, reorder and see titles, assignees, priorities at a glance. Filter and sort tickets by assignee, status, priority, issue type, tags, due date, and more.


# List
Source: https://docs.janet.ai/views/list

List view with tickets grouped by status

<div>
  <div>
    <div>
      <div>
        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>Mobile App</span>
        <span>MOB</span>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />

              <rect />
            </svg>

            <span>Kanban</span>
          </span>

          <span>
            <svg>
              <path />

              <path />

              <path />
            </svg>

            <span>List</span>
          </span>

          <span>
            <svg>
              <path />
            </svg>

            <span>Signals</span>
            <span>New</span>
          </span>
        </div>

        <span>
          <svg>
            <path />
          </svg>

          <span>Create</span>
        </span>

        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>
          <svg>
            <path />
          </svg>
        </span>
      </div>
    </div>

    <div>
      <div>
        <svg>
          <path />
        </svg>

        <span>
          <svg>
            <path />
          </svg>
        </span>

        <span>To Do</span>
        <span>2</span>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>SW-131</span>
          <span>Write API documentation for webhook endpoints</span>

          <span>
            <span>—</span>
            <span>Apr 12</span>
          </span>
        </div>

        <div>
          <span>
            <span>—</span>
          </span>

          <span>SW-128</span>
          <span>Research SSO providers for enterprise plan</span>

          <span>
            <img alt="" />

            <span>—</span>
          </span>
        </div>
      </div>

      <div>
        <svg>
          <path />
        </svg>

        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>In Progress</span>
        <span>3</span>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>SW-142</span>
          <span>Fix authentication token refresh on mobile</span>

          <span>
            <img alt="" />

            <span>Apr 3</span>
          </span>
        </div>

        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>SW-139</span>
          <span>Migrate billing service to Stripe v3 API</span>

          <span>
            <span>
              <img alt="" />

              <img alt="" />
            </span>

            <span>Apr 7</span>
          </span>
        </div>

        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>SW-136</span>
          <span>Add real-time presence indicators to editor</span>

          <span>
            <img alt="" />

            <span>—</span>
          </span>
        </div>
      </div>

      <div>
        <svg>
          <path />
        </svg>

        <span>
          <svg>
            <path />

            <path />
          </svg>
        </span>

        <span>Done</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>SW-124</span>
          <span>Set up CI pipeline for staging deployments</span>

          <span>
            <img alt="" />

            <span>Mar 28</span>
          </span>
        </div>
      </div>
    </div>
  </div>
</div>

View all tickets in a flat, scannable list. Drag to reorder tickets and see titles, assignees, priorities, and due dates at a glance. Filter and sort tickets by assignee, status, priority, issue type, tags, due date, and more.


# Signals
Source: https://docs.janet.ai/views/signals

AI-powered project analysis

Signals view buckets related tickets into objectives, flags tickets that need attention, finds duplicate issues to merge, and suggests action items.

## Objectives

<div>
  <div>
    <div>
      <div>
        <span>Objectives<span>4</span></span>
        <span>Needs Attention<span>5</span></span>
        <span>Duplicates<span>6</span></span>
        <span>Actions<span>3</span></span>
      </div>
    </div>

    <div>
      <div>
        <div />

        <span>High</span>
        <span>2</span>
      </div>

      <div>
        <div>
          <div>
            <div>
              <div>
                <span />

                <span />

                <span />

                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>
            </div>
          </div>

          <div>
            <span><span>To Do</span></span>
            <span><span>In Progress</span></span>
            <span><span>Done</span></span>
          </div>

          <div>API Rate Limiting Issues</div>
          <div><span>MOB-42</span><span>MOB-57</span><span>MOB-61</span><span>+10 more</span></div>
          <div>Multiple tickets reporting 429 errors and throttling behavior across API endpoints</div>
        </div>

        <div>
          <div>
            <div>
              <div>
                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />
              </div>
            </div>
          </div>

          <div>
            <span><span>To Do</span></span>
            <span><span>In Progress</span></span>
            <span><span>Done</span></span>
          </div>

          <div>Dashboard Loading Performance</div>
          <div><span>MOB-19</span><span>MOB-33</span><span>MOB-48</span><span>+6 more</span></div>
          <div>Slow initial load times and rendering lag on the analytics dashboard</div>
        </div>
      </div>

      <div>
        <div />

        <span>Medium</span>
        <span>2</span>
      </div>

      <div>
        <div>
          <div>
            <div>
              <div>
                <span />

                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />
              </div>
            </div>
          </div>

          <div>
            <span><span>To Do</span></span>
            <span><span>In Progress</span></span>
            <span><span>Done</span></span>
          </div>

          <div>Push Notification Reliability</div>
          <div><span>MOB-15</span><span>MOB-28</span><span>MOB-39</span><span>+6 more</span></div>
          <div>Intermittent push notification delivery failures on Android devices</div>
        </div>

        <div>
          <div>
            <div>
              <div>
                <span />

                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />
              </div>
            </div>

            <div>
              <div>
                <span />

                <span />
              </div>
            </div>
          </div>

          <div>
            <span><span>To Do</span></span>
            <span><span>In Progress</span></span>
            <span><span>Done</span></span>
          </div>

          <div>Biometric Auth Edge Cases</div>
          <div><span>MOB-31</span><span>MOB-44</span><span>MOB-52</span><span>+4 more</span></div>
          <div>Face ID and fingerprint auth failing on certain device models after OS update</div>
        </div>
      </div>
    </div>
  </div>
</div>

Janet AI automatically groups related tickets into named objectives. Objectives are sorted by urgency, and each card shows a status breakdown of its tickets, the ticket IDs it contains, and a short summary. Click any card to open it and see the individual tickets.

## Needs Attention

<div>
  <div>
    <div>
      <div>
        <span>Objectives<span>4</span></span>
        <span>Needs Attention<span>5</span></span>
        <span>Duplicates<span>6</span></span>
        <span>Actions<span>3</span></span>
      </div>
    </div>

    <div>
      <div>
        <span>High-Context Tickets</span>
        <span>2</span>
      </div>

      <div>
        <div>
          <div>
            <span>
              <svg>
                <rect />

                <rect />

                <rect />

                <rect />
              </svg>

              <span>MOB-42</span>
            </span>

            <span>2d overdue</span>
          </div>

          <div>Auth token refresh loop</div>

          <div>
            <span>Linked context</span>
            <span>7 items</span>
          </div>

          <div>
            <span>
              <img alt="Slack" />
            </span>

            <span>
              <svg>
                <path />

                <path />

                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <rect />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />
              </svg>
            </span>
          </div>
        </div>

        <div>
          <div>
            <span>
              <svg>
                <rect />

                <rect />

                <rect />
              </svg>

              <span>MOB-19</span>
            </span>

            <span>Due · Jul 18</span>
          </div>

          <div>Dashboard loading performance</div>

          <div>
            <span>Linked context</span>
            <span>4 items</span>
          </div>

          <div>
            <span>
              <svg>
                <path />

                <path />

                <path />

                <path />
              </svg>
            </span>

            <span>
              <img alt="Slack" />
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>

            <span>
              <svg>
                <path />

                <path />
              </svg>
            </span>
          </div>
        </div>
      </div>

      <div>
        <span>Stagnant Tickets</span>
        <span>3</span>
      </div>

      <div>
        <div>
          <span />

          <span />

          <span />

          <span>Last updated</span>
          <span>Status idle</span>
        </div>

        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>MOB-23</span>
          <span>Migrate settings page to new design system</span>
          <span>12d ago</span>
          <span>18d</span>
        </div>

        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>MOB-45</span>
          <span>Add keyboard shortcuts for ticket triage</span>
          <span>9d ago</span>
          <span>11d</span>
        </div>

        <div>
          <span>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>
          </span>

          <span>MOB-36</span>
          <span>Investigate flaky session timeout on Safari</span>
          <span>7d ago</span>
          <span>7d</span>
        </div>
      </div>
    </div>
  </div>
</div>

The **Needs Attention** tab surfaces tickets that are at risk of slipping:

* **High-context tickets**: tickets with lots of activity attached, like comments, code runs, and workspace documents, that may need a closer look.
* **Stagnant tickets**: tickets that have sat idle past your configured thresholds.

## Duplicates

<div>
  <div>
    <div>
      <div>
        <span>Objectives<span>4</span></span>
        <span>Needs Attention<span>5</span></span>
        <span>Duplicates<span>6</span></span>
        <span>Actions<span>3</span></span>
      </div>
    </div>

    <div>
      <div>
        <div />

        <span>Critical</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <svg>
            <path />

            <path />

            <path />

            <path />

            <path />

            <path />

            <path />

            <path />

            <path />
          </svg>
        </div>

        <div>
          <div>Login Page Redirect Loop</div>

          <div>
            <span>MOB-8</span>
            <span>MOB-17</span>
            <span>MOB-31</span>
            <span>+1</span>
            <span>\~96%</span>
          </div>

          <div>Users stuck in infinite redirect between login and dashboard when SSO session expires</div>
        </div>
      </div>

      <div>
        <div />

        <span>High</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <svg>
            <path />

            <path />

            <path />

            <path />

            <path />

            <path />

            <path />
          </svg>
        </div>

        <div>
          <div>Email Notification Failures</div>

          <div>
            <span>MOB-22</span>
            <span>MOB-35</span>
            <span>MOB-41</span>
            <span>\~93%</span>
          </div>

          <div>Multiple tickets describing email delivery failures for password reset and verification emails</div>
        </div>
      </div>

      <div>
        <div />

        <span>Medium</span>
        <span>1</span>
      </div>

      <div>
        <div>
          <svg>
            <path />

            <path />

            <path />

            <path />

            <path />

            <path />

            <path />
          </svg>
        </div>

        <div>
          <div>CSV Export Timeout</div>

          <div>
            <span>MOB-14</span>
            <span>MOB-29</span>
            <span>MOB-52</span>
            <span>\~89%</span>
          </div>

          <div>Data export fails or hangs on datasets over 10k rows across multiple export formats</div>
        </div>
      </div>
    </div>
  </div>
</div>

The **Duplicates** tab surfaces duplicate tickets within your project. Each group shows a similarity score, an explanation of the overlap, and lets you **merge** them into a single ticket with one click. Janet AI combines the descriptions, keeps the highest priority, and carries over all assignees.

## Actions

<div>
  <div>
    <div>
      <div>
        <span>Objectives<span>4</span></span>
        <span>Needs Attention<span>5</span></span>
        <span>Duplicates<span>6</span></span>
        <span>Actions<span>3</span></span>
      </div>
    </div>

    <div>
      <div>
        <span>Assign Tickets</span>
        <span>3</span>
      </div>

      <div>
        <div>
          <div>
            <svg>
              <rect />

              <rect />

              <rect />

              <rect />
            </svg>

            <span>MOB-38</span>
            <span>Add push notification settings</span>
          </div>

          <div>
            <div>
              <img alt="" />
            </div>

            <div>
              <div>Will Barthell</div>

              <div>
                <span><span>Assigned to </span>2 related tickets</span>

                <svg>
                  <path />
                </svg>
              </div>
            </div>

            <span>Assign</span>
          </div>

          <div>
            <div>Related Tickets</div>

            <div>
              <svg>
                <rect />

                <rect />

                <rect />
              </svg>

              <span>MOB-12</span>
              <span>Push notifications not delivered on Android 14</span>
            </div>

            <div>
              <svg>
                <rect />

                <rect />

                <rect />
              </svg>

              <span>MOB-27</span>
              <span>Silent push notifications ignored when app is backgrounded</span>
            </div>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>

            <span>MOB-41</span>
            <span>Localize date formats</span>
          </div>

          <div>
            <div>
              <img alt="" />
            </div>

            <div>
              <div>Adhit Sankaran</div>

              <div>
                <span><span>Assigned to </span>3 related tickets</span>

                <svg>
                  <path />
                </svg>
              </div>
            </div>

            <span>Assign</span>
          </div>
        </div>

        <div>
          <div>
            <svg>
              <rect />

              <rect />

              <rect />
            </svg>

            <span>MOB-34</span>
            <span>Design onboarding flow for new users</span>
          </div>

          <div>
            <div>
              <img alt="" />
            </div>

            <div>
              <div>Will Barthell</div>

              <div>
                <span><span>Assigned to </span>1 related ticket</span>

                <svg>
                  <path />
                </svg>
              </div>
            </div>

            <span>Assign</span>
          </div>
        </div>
      </div>
    </div>
  </div>
</div>

The **Actions** tab recommends assignees for unassigned tickets based on who's already working on related issues. Click **Assign** to apply it instantly, or expand to review first.


# Sprints
Source: https://docs.janet.ai/views/sprints

Organize your team's work into sprints

<div>
  <div>
    <div>
      <div>
        <span>
          <svg>
            <path />

            <path />

            <path />
          </svg>

          Active
        </span>

        <span>
          <svg>
            <rect />

            <path />

            <path />

            <path />
          </svg>

          Mar 24
        </span>

        <span>–</span>

        <span>
          <svg>
            <rect />

            <path />

            <path />

            <path />
          </svg>

          Apr 4
        </span>
      </div>

      <div>Sprint 14</div>

      <div>
        <div>
          <span>3 of 7 complete</span>
          <span>43%</span>
        </div>

        <div>
          <div />
        </div>
      </div>
    </div>

    <div />

    <div>
      <div>
        <span>Tickets</span>
        <span>7</span>
      </div>

      <div>
        <span>In Progress</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-128</span>
        <span>Fix auth token refresh on expired sessions</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-131</span>
        <span>Add rate limiting to public API endpoints</span>
      </div>

      <div>
        <span>In Review</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-125</span>
        <span>Migrate user preferences to Postgres JSONB</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-134</span>
        <span>Update changelog for v2.4 release</span>
      </div>

      <div>
        <span>Done</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-119</span>
        <span>Implement webhook retry with exponential backoff</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-122</span>
        <span>Add org member count to billing dashboard</span>
      </div>

      <div>
        <svg>
          <rect />

          <rect />

          <rect />

          <rect />
        </svg>

        <span>PRJ-116</span>
        <span>Fix SSO callback race condition</span>
      </div>
    </div>

    <div>
      <span>
        <svg>
          <path />
        </svg>

        Add tickets
      </span>
    </div>
  </div>
</div>

Sprints let you scope a fixed window of work within a project. Each sprint has a name, start date, end date, and a set of assigned tickets. A progress bar tracks how many tickets have reached a resolved column.

## Creating a sprint

Open the **Sprints** dropdown from the project header (or press **S**) and click **Create**. Give the sprint a name and pick a start and end date. A sprint's status badge updates automatically to **Active**, **Completed**, or **Overdue** based on the date range and whether unresolved tickets remain.

## Managing tickets

Click **Manage** on the sprint bar or the edit icon in the dropdown to open the sprint detail panel. From there you can add tickets via the side panel, which lists every ticket in the project not already assigned to a sprint, grouped by status. Search by title or ticket ID to find specific tickets. Remove a ticket by hovering its row and clicking the remove button.

When a sprint is selected and you click the **+** button in the project header, you get two options: **Create ticket** (opens the standard create modal) or **Add to \[Sprint]** (opens the manage panel directly).

## Viewing sprint tickets

Sprints integrate with both project views:

* **Kanban** -- Select a sprint from the dropdown to filter the board to only that sprint's tickets. A bar below the header shows the sprint name, date range, and a **Manage** link. The board automatically includes resolved tickets regardless of age so you can see the full sprint scope.
* **List** -- Toggle one or more sprints from the dropdown. Sprint tickets appear in their own collapsible section above the regular status groups, sorted by status then priority. Drag and drop tickets between sprints and status groups.

Your sprint selection persists per project across sessions.

## Using Janet to manage sprints

Ask the [Janet Agent](/agent) to handle sprint operations in natural language.

<CardGroup>
  <Card title="Create a sprint">
    "Create a sprint called 'Sprint 8' starting next Monday"
  </Card>

  <Card title="Add tickets">
    "Add SW-42 and SW-43 to Sprint 7"
  </Card>

  <Card title="View sprint tickets">
    "Show all tickets in the current sprint"
  </Card>

  <Card title="Create and assign">
    "Create 3 tickets for the auth feature and add to current sprint"
  </Card>
</CardGroup>