Linear is simple. Jira is detailed. We needed a third thing.

Linear wins speed. Jira wins process. Trello is a wall. Tides is a simple board with the extra detail a client project actually has: hours, a document, an inbox for the teammate.

Every comparison of Linear and Jira ends the same way. Linear is the racecar. Jira is the fortress. Cool. I do not run an engineering department. I run client work. The card has a person, a due date, a conversation, and later an hour someone has to invoice. Linear does not care about that hour. Jira will let you add pieces until the board needs a part-time admin.

Asana is in this conversation too. It is the cross-functional planner. Fine for marketing and ops portfolios. It still does not know the hour you just tracked. I left it out of the table because the real fork is simple versus detailed, and Asana sits in a third building.

What we kept simple

Statuses you can name. A board, a list, a timeline. Assign, comment, attach, move on. No workflow engine. No certification. If your team needs a meeting to add a column, the tool already lost.

What we kept detailed

The project belongs to a workspace and usually a client. Time can live on the card. A wiki page can hang off it. Shelly does not spray tasks into the void — it lands in a column called agent inbox, and a human can throw it back. That is the detail Linear treats as someone else’s problem, and the detail Jira buries under schemes.

What is actually wired

• Statuses you name, including a seeded agent inbox column for your teammate. Shelly’s intake is that column, not a second product.
• Time on a task feeds the shared hour record. The timer reports it. The card stays a board card.
• A “Track with the timer” shortcut carries the task, so you never retype the project name.
• Connected-app rules (admin or owner): an assigned issue can create a task. Incoming events are recognised once, so nothing doubles up.
• Projects and tasks can link documents. Search results still respect who may see the document.
• Team-chat notifications use their own scoped access, not your browser session.
• Board, list and timeline on the same project. Rich text on the card. Tags, templates, relations and attachments, stored privately.

I would rather be a slightly boring board that invoices than a beautiful issue tracker that cannot.

If you are twenty engineers and the work is the code, use Linear. Seriously. If a regulator wants Jira, use Jira. Tides is for the rest of us: the studio that has a board, a clock, and a client who does not care which framework you like.

Use Tides when you want Linear’s calm without pretending you are a code-only team, and Jira’s substance without hiring a Jira person.