How can we help?

A task tracker for a small team running several projects at once. Workspaces hold projects, each project has its own task prefix and workflow, and tasks, labels and activity live under them. Projects can also have a public board where people outside the team ask for things, vote, and follow a roadmap.

Yes. Anyone can sign up for Issuelane with an email address or a Google account. It is in preview and free while it lasts.

Sign up, then create a workspace. Add a project: it gets its own task prefix and a five-state workflow you can rename. Press C anywhere in the task list to file a task, and invite the rest of the team from Members.

With a link sent to your email address, or with a password if you set one. The address you sign in with is what identifies your account.

A workspace is the tenant: everything you can see belongs to one, and you can belong to several and switch between them. A team is a group of people inside a workspace. Your role in a workspace, which is owner, admin, member or guest, is what decides whether you can create a project or only browse.

A project is one of the things your team builds, and its prefix is the short code its tasks are numbered with, so a task reads as something like WEB-14 rather than as a bare number. Prefixes are unique within a workspace, and the form previews the identifier before you commit to one.

Every new project starts with Backlog, Todo, In progress, Done and Canceled. The names are yours to change; what does not change is the category each one maps to, which is what lets progress be read across projects that call their states different things.

Scope decides where a label may be used: a workspace label goes on any project's tasks, a project label only on its own. Changing it after the fact would strand labels on tasks they are no longer allowed on. The API refuses it, which is why the edit form shows scope as text rather than as a control that would fail.

Yes, if you are an admin. Deleting a label takes it off every task it is on and does not archive it, because a label is a piece of the workspace vocabulary rather than a record of anything, and what it said is already in each task's activity. A label group with labels still inside it is refused rather than leaving them behind.

Yes, from the filter bar above the list. It narrows by assignee, delegate, project, sprint, state, progress, priority, label, due date, whether a task has a parent, and free text. Every one of those is applied by the server across the whole workspace rather than to the page already fetched, which is what makes a filtered list a complete answer instead of the first page of one.

From the row controls, or with Alt and an arrow key. It is offered on a list filtered to one project with archived tasks hidden, and nowhere else: order is unique within a project, so a position across projects is not a position at all.

Yes. Press ? anywhere in the app for the full list. Cmd+K or Ctrl+K opens the command palette, and j and k move down and up the task list from anywhere on the screen.

Yes, through MCP. In Settings, open MCP access, create a token and choose what it may do: read only, or read and change tasks. The token is shown once, with the configuration for each of those five clients filled in; copy it into the client, which sends it in the Authorization header to your workspace's MCP address. The client then acts as you in that one workspace: it lists, searches, creates and updates tasks, comments, plans sprints and reads your inbox; sets tasks to repeat; saves views; searches the whole workspace; reads milestones, initiatives, the roadmap and insights; watches tasks, follows projects and changes how you are notified; and answers agents in their sessions. A read-only token is offered only the tools that read. Archiving, removing links and changing many tasks at once wait for your approval in the app first (see the next answer). If you are a workspace admin or owner, a third choice lets the client set the workspace up as you: create and change projects and their areas, labels and initiatives, and change a milestone or link it to an initiative. Deleting an area waits for your approval, like archiving a project. Creating and deleting milestones, members and every other admin setting stay in the app. Every change is recorded under your name. A token expires after the days you chose, at most a year, and Revoke stops it at once. Admins give an agent its own token the same way under Agents. Clients that need an OAuth sign-in, such as the web version of Claude, cannot connect yet.

Archiving a task or a project, removing a link between tasks and changing many tasks at once never run straight from a token, an agent's or your own. The client is given a link instead, and the person behind the token is told in their inbox and by email: you for your own token, the person who issued an agent's token (or the workspace admins if they have left). Archiving a project has no task to file a notice under, so open the link the client gives you or find it under Settings, Approvals. Open the link while signed in to see exactly what would change, read from the tasks or project as they are now, then approve or deny it. Only a person signed in to the app can decide; no token can. Once approved, it runs the next time the client checks on it, or at once if you choose Approve and run now, for an agent that will not come back to ask. If a task it touches changed in the meantime it does not run, and the client has to ask again. A request nobody decides expires after 24 hours. Settings, Approvals lists what is waiting and what was decided, and the audit log records every call, request and decision.

Open a project, go to its Requests tab and choose Board settings. Turn the board on, check its address and title, and save. The board lives at /p/ followed by your workspace and board addresses. Only workspace admins can change these settings. Turning a board on publishes nothing that already exists: ideas filed in the app stay private until an admin posts one to the board.

Anyone with the link can read the board, its requests and the roadmap, without an account. Posting a request, voting, following and commenting need a signed-in account, which does not have to belong to your workspace. Your team appears on the board as your workspace's team, never by name, and nobody's email address is shown.

New requests wait in the Requests tab under Needs review until an admin accepts or declines them. Accepting puts a request on the board with its number. Declining keeps it off, and the person is not notified; you can block them at the same time. You can also merge a request into another one, which moves its votes and followers there, hide a request, or promote it to a task in the same project. If you prefer, a board can publish new requests right away, marked under review.

Link a request to a task, by promoting it or linking an existing task, and the board follows the task: planned while the task is waiting, in progress once it starts, shipped when it is done. Nobody moves requests on the roadmap by hand. The roadmap shows the statuses your board settings make public.

Your email address, the account id we give you and, if you set a password, a salted hash of it, plus the work itself: workspaces, teams, memberships, projects, tasks, labels and the history of changes to a task. Nothing is bought from anyone and nothing is sold to anyone.

No. There is no analytics library in the application at all today, and no advertising anywhere. The consent banner asks anyway, because the answer should be recorded before the question has consequences rather than after, and your browser's Global Privacy Control signal is honoured before you are ever asked.

Yes. An admin uploads a workspace archive, or a CSV export in the format the import screen names, from Import and export in settings. The file is checked first and you see what importing it would create before anything is written, and importing the same file twice updates the same records rather than copying them.

Yes. An admin can download the whole workspace from Import and export in settings: projects, workflow states, labels and tasks, archived ones included. Comments, attachments and relations are not in the file yet, and nothing has yet tested that exporting a workspace and importing it back returns the same workspace, so it is a copy of your data rather than a restore.

Nothing, while Issuelane is in preview. The plans are published so the eventual cost is not a surprise, and every one of them is free today. There is no card form, no invoice and no subscription to cancel.

Write to us. Plan changes are not self-serve, because there is nothing to change between yet: every workspace is on the same footing during preview.