Jira issue done, told in Slack starts a run when an issue moves to the status you choose, such as Done, and posts it in a Slack channel with its key, summary, who it's assigned to and a link. This article shows how to install it and fill in each step.
Who can do this
Workspace Admins and Editors. Templates are on every plan. Jira ◇ is on paid plans: on Free you can set the template up and test it, and publishing asks for a paid plan. See Premium connections on the Free plan.
Before you start
- A Jira connection. See Connect Jira.
- A Slack connection. See Connect Slack.
Steps
Install it
- On Workflows, select the arrow beside + New workflow, then From a template.
- In Search templates, type Jira.
- On Jira issue done, told in Slack, select Use this template.
- In Install into, choose the workspace or project, then select Install as a draft.
- The toast says Installed as a draft, for example Jira issue done, told in Slack is in Consulace. Connect Jira and Slack, then publish. An app it doesn't name had one connection in the workspace, and the template has chosen it. Select Open it. The workflow opens in the designer with two steps.
Fill in the steps
- Select When an issue is done (Jira · Issue moved to a status).
- Choose the Jira Connection, then the Project.
- In Status, choose your done status, such as Done or Released.
- JQL filter is optional, such as
issuetype = Bugto post only bugs.
- Select Tell the channel (Slack · Post a message). Choose the Slack Connection and the Channel, such as #releases.
- Select the trigger, open Output and select Fetch a sample. The newest matching issue comes in, and Test run starts with it. Then select Test run. See Testing a workflow before you publish it. The message is really posted.
- Publish the workflow and switch it on.
What happens next
- Jira is checked every 5 minutes on a paid plan. Each issue that moved to the status since the last check starts one run.
- The first check after publishing only notes the time. Issues already in the status never start a run, only ones that move to it after you publish.
- An issue that leaves the status and comes back between two checks starts one run, for its latest move.
Good to know
- If an issue has moved on again by the time it's checked, the message shows the status it's in now.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Steps marked Needs setup | A connection, project, status or channel isn't chosen yet | Open each one and fill it in. See Fix steps marked Needs setup. |
| Publishing says "“When an issue is done” needs a paid plan. Change the plan, or remove it and publish the rest." | Jira is a premium connection and the company is on Free | Change to a paid plan once they're open. |
| The trigger shows Not checking since 10:45, with Jira refused: … | Jira refused the check, for example because the token has expired | Select Reconnect and fill in a new token, then Check now. See When an app trigger stops checking. |