Task integrations
Silktide can with the task tracker your team already uses: Jira or Linear. Connecting one means an accepted Silktide task becomes an issue in that tracker, so the work is picked up where people already look.
You only need one tracker connected. Account administrators connect it from Settings → Integrations, or from the prompt at the top of Tasks.
What connecting does
- Authorises Silktide to create and update issues in your tracker on your behalf.
- Asks where tasks should go: a Jira site and project, or a Linear team.
- Sends a task when it becomes real work: when you accept a proposed task, create one straight into a working status, or reopen a cancelled one. Its title and description become a new issue that links back to the task in Silktide, in the status that matches the task's. Open in Jira or Open in Linear on the task opens its issue.
- Carries later changes to the task's title, priority, and status over to the issue. The description is not updated once the issue exists.
Proposed tasks never leave Silktide. Accepting is what sends them, which keeps untriaged suggestions off your team's board. Connecting does not change how you create tasks in Silktide: Silktide remains where the finding was turned into work, and the tracker is where that work is run.
Finish setup
Right after you connect, Where should tasks go? asks for the destination. Until it is saved, the integration shows Needs setup and nothing is sent. Finish later lets you leave it; Finish setup on the integration or on Tasks brings you back to it.
Tasks accepted before you connected
Tasks you accepted before connecting are not sent on their own. Once setup is done, the integration offers them, such as "3 accepted tasks are not in Jira yet", and Send them to Jira sends them. Nothing goes until you choose to.
When a send fails
If a task could not be sent or updated, its sidebar says why, with Try again. When the destination is missing, someone who manages integrations can choose it right there with Save and send.
Jira
Silktide sends tasks to Jira and keeps each issue's title, priority, and status in step with its task. Changes made in Jira stay in Jira: they do not update the task in Silktide.
Connecting. Authorise Silktide for your Atlassian site. If you can reach several sites, choose the one tasks go to. Then choose the Project; Silktide suggests the project with the most recent activity. Issue type can stay on Automatic, which uses the project's Task type, or its first standard type if it has no Task.
Priority. Silktide's priorities become Jira's Low, Medium, High, and Highest. A task with no priority takes the project's default. In a project that does not use priorities, the issue is created without one.
Silktide never deletes a Jira issue. When a task goes back to proposed, is cancelled, or is deleted in Silktide, its issue is withdrawn instead:
- An issue still in a To Do status moves to a status such as Cancelled or Won't Do, if your workflow has one. Jira's default workflows don't, and the issue then stays where it is.
- An issue someone has already started or finished is never moved.
- Every withdrawn issue gets the
silktide-withdrawnlabel, so your team can filter them out, and a comment saying why.
Linear
After you connect Linear, choose a default team, and optionally a project within it. Until a team is set, Silktide cannot send.
Changes to a task's title, priority, and status in Silktide are carried over to its Linear issue. Changes made in Linear stay in Linear. When a task goes back to proposed, is cancelled, or is deleted in Silktide, its Linear issue is deleted.
Disconnecting
Disconnect on the integration revokes Silktide's access to your tracker and removes the stored credentials. Silktide stops sending, and issues already created stay in your tracker. You can reconnect at any time.