A task is one piece of work for CodeLynq: a feature, a bug fix, a refactor, a chore or an investigation. Each task belongs to a project, gets a spec that you approve, and ends in one or more pull requests.
Create a task
There are three ways:
- The new-task chat - click New task at the top of the sidebar or press ⌘K / Ctrl K, and describe what you need. The assistant asks what is missing and proposes a complete task. This is the quickest way. See Create a task by chatting.
- Quick form in a project - open the project, and on its Tasks tab click New Task. Fill in Task title, Description, Type and Priority, and click Create Task.
- The full task form - click New task at the top of the Tasks page, or More options in a project's quick form. Besides the fields above it lets you choose the Repositories and Branches, the Troubleshoot type and, for bugs, a structured bug report.
Tasks also arrive from meeting notes, epics, alerts, backlog grooming, integrations and external AI clients.
Type
- Feature - something new.
- Bug Fix - something broken. See below.
- Refactor - improve the code without changing what it does.
- Chore - maintenance, such as upgrading dependencies or configuration.
- Troubleshoot - you do not know the cause yet. Instead of a spec and a run, it opens a read-only investigation that ends in a diagnosis. See Troubleshooting.
Priority
Low, Medium, High or Critical. Priority helps you and your team order the work; backlog grooming can propose priorities for you.
Reporting a bug
With the type Bug Fix, the full form adds a Bug report section:
- Steps to reproduce
- Expected behavior
- Actual behavior
- Stack trace / error output (optional)
- Failing test or snippet (optional)
The AI first reproduces the bug - writing a failing test where possible - then finds the root cause, fixes it and verifies the fix before opening a pull request. The more precise the report, the more reliable the fix. In the new-task chat, just describe what you did, what you expected and what happened; the assistant asks for anything missing.
Repositories and branches
In the full form, tick the Repositories the task should change; leave them all selected to include the whole project. Under Branches you can apply the task to several version or release branches at once, with one pull request per branch. See Work on several branches at once and Maintained branches.
The task page
At the top, Progress shows where the task stands - Task, Spec, Approved, Building, Pull request, Done - with the next step and a button for it. A finished run is not a finished task: done means merged, or marked done.
Open a task to see its tabs:
- Overview - the description, details (type, priority, status, created, repositories), Branches, Dependencies and the Latest Run with its pull request.
- Spec - the technical solution design. See The spec (TSD) and approval.
- Validation - a chat about the spec.
- Runs - the development runs and their pull requests. See Runs.
- Troubleshoot - a read-only investigation, also available for normal tasks.
A Troubleshoot task has only Overview and Investigation.
Dependencies
Under Dependencies on the Overview tab, click Add, search for a task in the same project and select it. Remove a dependency with ✕. Dependencies record which tasks this one builds on; in an epic, tasks run in dependency order.
Status
A task moves through these statuses:
| Status | Meaning |
|---|---|
| Draft | Created, no spec yet. |
| Drafting spec | A spec is being written. |
| Validating | The spec is being discussed. |
| Needs approval | The spec was submitted and waits for approval. |
| Approved | The spec is approved; a run can start. |
| In progress | A run is working on it. |
| PR open | A pull request is waiting for review. |
| Done | Every pull request of the latest run is merged. CodeLynq sets this itself: at once with the repository's CI webhook, otherwise by asking your git host every ten minutes and whenever you open the task. A pull request closed without merging shows as Closed without merge and does not make the task done. Mark as done… sets it by hand, after a confirmation. |
| Failed | The last run failed. You can retry it. |
| Investigating / Diagnosed | For troubleshoot tasks: under investigation, or a diagnosis is ready. |
Find tasks
Tasks in the sidebar lists every task across your projects. Filter by status, type, priority and project, or tick Group by project. Tick Archived to see archived tasks instead. Clear filters shows everything again. The tiles on the Dashboard link to filtered lists as well.
Archive or delete
Both are under More at the top of the task page.
- Archive hides a task from the task lists without deleting anything. To find it again, tick Archived on the Tasks page; open it and click Unarchive to bring it back.
- Delete removes the task permanently, with its specs, mockups, runs and comments, after confirmation. Pull requests and branches on your git host stay. This cannot be undone; the confirmation offers to archive instead.