Using sjTasks
Short pages, one question each. Start at the top if sjTasks is new to you, or search for the thing you are trying to do.
Getting started
What sjTasks is and how to get your first work into it.
- What sjTasks is The shape of the whole product in five minutes: teams, projects, tasks, and the files, notes and time that hang off each task.
- Starting a team Starting a team takes a minute: what you enter, the code that confirms your address, naming your team or joining one that invited you, and the Free plan.
- Your first project From an empty team to real work in about two minutes: make a project, put tasks in it, and tell the people who need to know about it.
- Project templates The shape of a job you run more than once, kept as a template, so the next project starts with its task lists and tasks already laid out.
- Importing your work Bring projects, tasks, notes and dates over from a spreadsheet, a board export or a project export — without retyping any of it.
- The dashboard Your plate as six counts and one list, plus what's new on the team and the questions you keep, across every project you can see.
Doing the work
Projects, tasks, and everything you hang off them.
- Projects, task lists, tasks, and subtasks Which one do I use for this piece of work? When to make a project, a task list, a task or a subtask, with rules of thumb and examples.
- The board The same project laid out by status: five columns, one card per task, and a task dragged to another column changes where it stands.
- The calendar The same project laid out by due date, so you can see what this month is going to feel like before you promise anyone anything.
- Adding tasks fast One line, one task: the shorthand for owner, priority, estimate, due date and tags, and the rules for what the box understands.
- Priorities and Some Day What the five priority levels mean, why every task starts at Medium, and where Some Day work goes so it neither nags you nor gets lost.
- Due dates, estimates, and logging time Due dates, estimates and hours logged: how the three differ, how to read the hours back, and how to switch time tracking off entirely.
- Notes on tasks The discussion, kept where the work is: how to write a note on a task or a project, edit one, mention someone, and what happens to it.
- Files on tasks Attaching a file to a task, what kinds are allowed, how big they can be, opening one without downloading it, and what happens when you remove one.
Finding things and answering questions
The Tasks table, the filters, and the views you keep.
- Finding things The search box and the Tasks table: sorting, grouping, the five menus, date windows, bulk edits, CSV export, and why every view is a link.
- Tags One word on a task or a project — #design, #retainer — and every list, board and report that can narrow to it, including each tag's hours against the rest.
- Custom fields Your own fields on tasks or projects — a budget, a PO number, a stage picked from a list — on the page, in the filters, the columns and the spreadsheets.
- Ask in your own words Type a question like "what did Sandy finish last week?" and the Tasks filters set themselves. What the AI does, and what it never does.
- Saved views and the standard questions The nine questions every team can already answer, how to save your own views, and how a saved view can email itself on a schedule.
People, access, and being told
Who can see what, who hears about what, and how to bring a client in.
- People, roles, and who sees what Admins, members, field workers and guests; inviting someone by email; letting a guest into one project or one client; and when someone leaves.
- Signing in and two-step sign-in Your password and one more proof it is you: codes by email, text or an app, recovery codes, a forgotten password, and the way back in when you are locked out.
- Your account Your name, email address and password; your timezone and clock; your address for tasks by email; text messages; where you are signed in; and leaving a team.
- Clients Group projects by the organisation they are for, and give a guest a whole client — every project of it, including the ones you add later.
- Tasks that need approval The switch that makes one person's new tasks wait for an admin: what both sides see, why Urgent goes straight through, and how waiting work is counted.
- Watchers Following work you do not own: watchers are set on the project, inherited by its tasks, and adjustable one task at a time.
- Notifications and summaries The bell, the emails, the daily and weekly summaries, due-soon and overdue reminders, and exactly which switch turns each one off.
- Replying by email Reply to any email about a task and your reply becomes a note on it: no signing in, no copying and pasting, and nothing to set up first.
- Exporting your team Export your tasks and everything else in your team at any time: every task, note, hour logged and file, exactly as uploaded. The link works for seven days.
Integrations
The tools your team already uses, and what crosses between them and sjTasks.
- Slack Slack is optional: a project's news in a Slack channel, what stays in Slack, and when to keep the conversation on the task in sjTasks.
- Setting up Slack Connect a project's Slack channel with an incoming webhook, choose what the channel hears, and what happens if it stops or you disconnect.
- Tasks into Gitea, and back Connect a project to a Gitea repository: a task you send opens as an issue there, and an issue a developer labels for you becomes a task here.
- Tasks into GitHub, and back Connect a project to a GitHub repository: a task you send opens as an issue there, and an issue a developer labels for you becomes a task here.
- Tasks into GitLab, and back Connect a project to GitLab, on gitlab.com or your own server: a task you send opens as an issue, and an issue labelled for you becomes a task.
Account and billing
The plans, what a person is, and what happens at the edge of one.