Integrations
Works with the tools your team already has.
Three integrations, each set up per project on its Integrations page by an admin. Every card below says what crosses over and what does not, because the second half is the part that keeps a client's view of the work plain and a developer's view technical.
Slack
A project's news goes to a Slack channel you choose, with the content in the message, through a webhook you make in Slack in a few minutes.
What does not cross: anything else said in Slack stays in Slack.
How to set it up →Reply to any notice and the reply becomes a note on the task. Every project can have its own address, shown on its Integrations page: forward an email to it and the subject is the task, the body its description, the attachments its files.
What does not cross: mail from anyone not on the team. It is left where it is.
How it works →GitHub, GitLab and Gitea
Connect a project to a repository on GitHub, GitLab or Gitea. A task you send there becomes an issue, with the description and a link back, and the two keep each other in step: title, status, assignee, and the client's notes as comments with the writer's name. An issue a developer labels for the client becomes a task here, and closing it marks the task done.
What does not cross: anything nobody sent. A task without the tag stays a task, an issue without the label stays an issue, and the developers' comments stay in the repository unless a developer shares one — a client never reads a stack trace.
Built for development shops
Your developers work in the repository. Your clients work here. The same task, typed once. How a developer shop runs its clients on sjTasks.
Every integration is on every plan. Start free — no card needed.