Where are the burndown charts?

There are none, on purpose. A curve drawn through guesses looks like data and gets treated like it. Instead, every project shows how many of its tasks are done, the number opens the list of what landed, the board counts what finished, and the Workload report says who is carrying what and what is late — real counts of real work, nothing projected.

Can I send someone a direct message?

No. A private message hides a decision from the project it belongs to, and three weeks later nobody can find why something changed. Instead, write a note on the task or on the project, where it stays with the work, and mention the person by name so they are told. A guest reads only their own project, so a client never sees another client's notes.

Is there a phone app?

No, and we would have to build it twice and update it forever. sjTasks is a web page: there is nothing to install and nothing to update, it opens in the browser on a laptop or a phone, and the version you see is always the current one.

Is there a public API?

Not yet; it is on our list, at the bottom, because most of what people want an API for has a plainer door. Today you can export the tasks table with your filters and columns, take your whole team home at any time — the data, the notes, the time and the files — and connect a project to a GitHub, GitLab or Gitea repository so tasks and issues stay in step.

Where is the dependency chart?

We draw no chart of arrows, because the arrows go stale the week after somebody draws them. Instead, a subtask can block its parent — the parent cannot be marked done while it is open, and says so — and a task that is waiting on something is marked blocked, with a note saying what it is waiting on, which is the one dependency people actually need to see.

Is there a Gantt view?

No. A Gantt chart makes a plan look more settled than it is, and it takes an afternoon to keep honest. Instead, each project has a calendar of its tasks by due date, and the dashboard counts what is due this week and next, with the dates printed on the cards, so the question a Gantt is opened to answer — what lands when — has an answer that does not need maintaining.

Features

The work in one place, and straight answers about it.

sjTasks holds your projects, tasks, files, and the conversation around them — then answers the questions you would otherwise spend a status meeting asking. Here is what that means, feature by feature.

Projects that stay legible

Every project has a short key and a number, so acme-142 means the same task in an email, in a report, and in a hallway. Rename a project and the old references keep working. Group work inside a project with task lists. Archive what is finished. Every team starts with a General project, so nothing has to wait for someone to set up structure first — and a new project can start from a template: one of ours, or a project of yours saved as one, lists and tasks laid out.

Tasks with one clear owner

A priority, a due date, an estimate, one owner, and a status that says where it stands: open, in progress, blocked, on hold, done, or canceled. Break work into subtasks one level deep, each with its own owner and date — and mark a subtask as blocking, so the parent refuses to close while it is still open. Watchers follow anything they care about.

Add a task the way you would say it

Type Draft the invoice @sam friday !high ~2h and get a task with an owner, a due date, a priority, and an estimate. Anything it could not read stays in the title with a note attached, so nothing you typed disappears quietly.

Your dashboard

One list of everything assigned to you across every project, in date order, in your own timezone. Parked work sits under a Some Day priority that is filtered out by default — visibly, so you always know it is there rather than wondering where a task went.

Files where the work is

A real folder tree per project, plus attachments on the task they belong to. Downloads go out on short-lived private links, deletes land in a trash you can undo, and each team has a storage quota it can see. No more "which folder was the final one in".

Ask it the way you would say it

The question is the report. What did Sandy finish last week? What is on Joe's plate this week? What is late in the Acme project? Who has more than they can do by Friday? Each one is a couple of menus on one screen, and each answer is a list you can send to someone. Save the questions you ask often and they wait for you on your dashboard.

More when you need it, not before

A new team's task shows its status, priority, who has it, when it is due, whether it repeats, and tags. Estimates, subtasks, watchers, time logging and fields of your own (a budget on each project, a stage picked from a list on each task) are all there, and all stay out of the way until you switch them on — and when something is off, its fields do not appear at all. Time tracking is the example people ask about first: hours logged by hand against a task, compared with the estimate, no running timers, nothing watching anyone work. Off by default. One switch for the team, and any one project can be set the other way.

Give a month, get a month

Every team has a referral link. Send another team to sjTasks with it and, when they start paying, their first paid month is on us — and so is your next one. A client of yours who starts a team of their own from their project counts too, without anyone sending anything. How it works.

Everyone sees the right amount

Admins run the team. Members do the work, either across the team or on named projects only. Guests read and add notes on the projects you choose — the setting for a client who should see their own project and nothing else. Every action is recorded with who did it and when.

Notifications that stay useful

Choose what reaches you and how. Bursts of related activity arrive as one message rather than nine, and you can take everything as a daily or weekly digest instead. Nothing emails you about something you just did yourself.

Times that mean what they say

Every date is stored once and shown in each person's own timezone, and your team decides whether a week starts on Monday or Sunday. "Due today" means today where the person reading it is sitting.

Works with the tools your team already has

A project's news can go to a Slack channel. Reply to any notice by email and the reply is a note on the task; forward an email to a project's own address and it is a new one. Connect a project to a GitHub, GitLab or Gitea repository and the tasks you send become issues, the client's notes become comments, and done closes the issue — in either direction. Each connection is set up per project, and each is on every plan. What crosses and what does not.

On purpose

Things we chose not to build, and what we do instead

Every one of these is a real question a buyer asks. "We don't have it" is a weak answer; here is why, and what you get in its place.

Where are the burndown charts?: There are none, on purpose. A curve drawn through guesses looks like data and gets treated like it. Instead, every project shows how many of its tasks are done, the number opens the list of what landed, the board counts what finished, and the Workload report says who is carrying what and what is late — real counts of real work, nothing projected.
Can I send someone a direct message?: No. A private message hides a decision from the project it belongs to, and three weeks later nobody can find why something changed. Instead, write a note on the task or on the project, where it stays with the work, and mention the person by name so they are told. A guest reads only their own project, so a client never sees another client's notes.
Is there a phone app?: No, and we would have to build it twice and update it forever. sjTasks is a web page: there is nothing to install and nothing to update, it opens in the browser on a laptop or a phone, and the version you see is always the current one.
Is there a public API?: Not yet; it is on our list, at the bottom, because most of what people want an API for has a plainer door. Today you can export the tasks table with your filters and columns, take your whole team home at any time — the data, the notes, the time and the files — and connect a project to a GitHub, GitLab or Gitea repository so tasks and issues stay in step.
Where is the dependency chart?: We draw no chart of arrows, because the arrows go stale the week after somebody draws them. Instead, a subtask can block its parent — the parent cannot be marked done while it is open, and says so — and a task that is waiting on something is marked blocked, with a note saying what it is waiting on, which is the one dependency people actually need to see.
Is there a Gantt view?: No. A Gantt chart makes a plan look more settled than it is, and it takes an afternoon to keep honest. Instead, each project has a calendar of its tasks by due date, and the dashboard counts what is due this week and next, with the dates printed on the cards, so the question a Gantt is opened to answer — what lands when — has an answer that does not need maintaining.

Nothing to install, nothing to run

sjTasks is a web application we host and look after. There is no server to buy, no software to update, no backup you have to remember. You open a browser and it is there — on a laptop, a phone, or somebody else's machine while you are out.

We run the backups, keep the certificates current, and apply updates without asking you to schedule downtime. Your data stays yours — one button in Team settings exports all of it, at any time, for any reason, including on your way out.