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 channel you choose — new tasks, notes, status changes, with the content in the message. In that channel, /sjtasks Fix the nav @jane !high friday makes a task the way it would anywhere else, and mentioning the app does the same.
What does not cross: replies in Slack stay 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 →Gitea
Connect a project to a repository. The tasks you choose — every one, or only those with a label — become issues, with the description and a link back. Notes on the task become comments on the issue, with the writer's name. Done closes the issue; in progress and blocked are labels on it.
What does not cross: nothing comes back into sjTasks yet. The developers' comments stay in the repository, and a client never reads a stack trace.
How to connect →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 for free.