Projects and tasks
Project management for freelancers, where every task has a client attached.
Plan the work, break it into tasks and milestones, and track progress. The difference from a standalone board is that the work knows who is paying for it, so delivery and billing stop being two separate systems.
What it does
Projects and milestones
Structure an engagement into stages you can deliver and bill against.
Tasks and assignments
Plan what has to happen and, on Team, who is doing it.
Hours on the task
Time logs against the task, so the cost of a milestone is recorded, not estimated.
Progress the client can see
Publish status to the portal so the client checks it instead of messaging you.
A board that knows who is paying
A task on a standalone board is a card. It does not know the client, the agreed scope, the rate, or the invoice it should end up on, so somebody carries that context in their head and re-enters it at billing time. Here the project descends from the proposal the client approved and the contract they signed, the hours land on its tasks, and a completed milestone becomes an invoice from work already recorded. Delivery and billing are one chain.
What it does not do
Worth knowing before you switch, so you are not surprised later.
Sprint ceremonies and agile reporting
No burndown charts, velocity, or story points. This is client delivery, not an engineering process tool.
Gantt-heavy resource planning
There is no capacity planner for a department. It suits an engagement you can hold in your head.
A git or issue-tracker integration
If your team lives in an issue tracker, keep it, and use Qivora for the client-facing layer: scope, hours, portal, and billing.
Common questions
Can I bill a milestone instead of hours?
Yes. Invoice a milestone on completion. Tracked time still runs underneath, which is how you learn afterwards whether the milestone price was right.
Will this replace my issue tracker?
For solo client work, usually. For a team already living in a tracker, probably not, and you do not have to choose: keep the tracker for engineering detail and use projects here for the client-facing layer.
Can the client see the project?
They see what you publish to the portal, which is progress and status, not your internal task detail, your rates, or your time entries.