Workspace

Board

A board is a set of columns with cards, filed under a group or a project. A card is a ticket. A board can hold only its own local cards, or it can sync with the issues and pull requests of a GitHub or GitLab repository, or with a Jira board. Use it to plan work, start sessions on tickets and review pull requests without leaving Clauge.

Board with columns and cards.

Project boards and group boards

Project board Group board
Filed under One project A group
Source The project's repository You choose: Manual, Jira board or Repo issues
Code actions (create issue, open PR, PR viewer) Available once the project has a linked folder Not available

Create a board

  1. Open a group or project and choose New board.
  2. Enter a Name.
  3. On a group board, pick a Source:
    • Manual: cards exist only in Clauge
    • Jira board: pick the Jira site and the Board
    • Repo issues: paste the Repository URL
  4. Select Create board.

Jira and repository sources need a connected account. Connect one under Settings › Workspace › Integrations.

To change what a board points at later, open the board options menu and choose Board links. There you set the Code repo, the Issue source (Same as code repo, Repository or Jira) and the Review / PR target.

Add and move cards

  1. Type a title in + Add a card at the bottom of a column, or select New ticket next to it for the full form.
  2. In the full form, fill in Title, Description, Tags and an optional Image, then select Create ticket.
  3. Drag a card to another column to change its status.

A card that exists only in Clauge is marked local. To turn it into an issue on the repository, right-click the card and choose Create issue on GitHub (or GitLab).

To mark which column means finished, open that column's options and choose Use as Done column. Issues closed on the host are hidden by default. Use Show closed to list them and Reopen to bring one back.

Sync issues and pull requests

  1. Open a board that is linked to a repository or a Jira board.
  2. Select Sync on the board toolbar.
  3. Select it again whenever you want to refresh.

Issue sync supports GitHub and GitLab repositories, and Jira boards.

Search, filter and group

Control Options
Search Searches tickets and pull requests
Filter Assigned to me, Unassigned, label, milestone, priority, Has PR. Clear removes all filters
Group cards by Status, Assignee, Label, Milestone, Priority
Compact Smaller cards

Label, milestone and priority appear only when the board's source provides them.

Open a card

Click a card to open it in a side drawer. The top line shows when it was created, its issue, its branch and any linked pull request. You can edit the title, description, tags and, on synced cards, assignees, labels, milestone and priority. The description saves as you type.

The drawer has three tabs:

Tab What it holds
Discussion The ticket's comments. On a synced card, comments are posted to the issue and everyone on it can see them. Save as private note keeps a comment in Clauge only
Co-workers A private chat with coworkers. Type @ and a coworker's name to ask one to work on the ticket. See Coworkers
Activity Linked pull requests, cross-references and a timeline

From a card to a pull request

  1. Start work on the ticket. Either pick it under Ticket when you create a session, or mention a coworker on the card's Co-workers tab.
  2. When the branch has commits, open the card and select Open PR….
  3. Check the Branch, Title and Body, then select Open PR.
  4. After that, the card shows View PR and Push update to PR for later commits.

Review pull requests

  1. Switch the board header from Board to Reviews.
  2. Choose Open or All. Open pull requests are grouped into Waiting on you, Your pull requests, Drafts and Other open.
  3. Click a pull request to open it in the PR viewer.

The PR viewer has five tabs: Review, Conversation, Commits, Checks and Files. From it you can comment, Approve, Request changes and Merge. On the Review tab, Ask a coworker to review starts a coworker review. Its comments stay as drafts until you select Post review.

AI-DLC on organization boards

In an organization group that has a development standard in force, each card shows its AI-DLC stage and state, for example Blocked or Needs work with the reason. A Blocking rule stops the action until the stage passes. AI-DLC does not apply in private groups.

When actions are unavailable

  • Group board: code actions are off. Use a project board for issues, pull requests and the PR viewer.
  • Project with no linked folder: code actions are off until you link a folder. See Projects.
  • No connected account: sync and pull request actions ask you to connect GitHub, GitLab or Jira in Settings first.

What’s next