Integrations
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.
A project can post its news into a Slack channel. It is there for a team that already spends its day in Slack and wants to see a project move without opening sjTasks. A project admin connects it on the project's Integrations page — see Setting up Slack.
The channel is a window on the work, not where the work lives. Notes, decisions and files stay on the task, and who is told what inside sjTasks does not change: that is still watchers and notifications.
What gets posted
Each event the admin ticks for the channel posts one plain line: who did what, the task reference as a link, the title after it. A note is quoted underneath in full, up to about 3,000 characters, with the link holding the rest of a longer one. Someone working through a task produces one message listing each change, not a message per change. Files added to a task are named in the message, and the link opens the task they are on.
Every event from notifications that makes sense in a room can be ticked; the two summaries are email only, and a mention is not its own line — the note that carries it is posted anyway.
A note you would rather keep out of the room can be: tick Keep this off Slack under the note before you add it. The note is saved and people are told as usual; only the channel does not see it. The box appears only on tasks in a project whose channel hears notes.
What stays in Slack
A channel connected with a webhook runs one way: sjTasks posts, and nothing said in Slack comes back. A reply in the channel is not a note on the task, and nobody is told about it in sjTasks.
If your team has added the sjTasks app to Slack (an admin does it in Team settings → Slack), two things do come back. A reply in the thread under a task's message becomes a note on that task, from the person who wrote it, and people are told about it as for any note. A task can also be added from the channel. Either works only for someone on your team whose Slack email is the one they sign in to sjTasks with. Everything else said in the channel stays in Slack.
If it matters to the work, it belongs on the task.
Slack or sjTasks?
Both can carry a project's news. Only one keeps the record.
Keeping the conversation on the task
- The decision sits with the work it is about, and whoever opens the task next month reads it.
- Your clients see it. A guest reads and writes the notes on the projects they are in; they are not in your Slack.
- It is found by search and goes home in the export.
- It reaches people the way each of them chose — the bell, email, the daily and weekly summaries — and anyone can answer from their inbox by replying to the email.
- It is one place to look.
A Slack channel
- Suits a team that already lives in Slack: the news arrives where they are.
- Gives quick awareness — a glance at the channel shows what moved today.
What a channel costs
- A decision made in the channel, outside a task's thread, stays in Slack, away from the task, and nobody reading the task sees it.
- Clients are not in the channel.
- It is one more place to look.
The two work together when the channel carries the news and the conversation happens on the task.