Jira logo
Slack logo

Workflow template

Notify Slack about new Jira issues

Announce newly created Jira Cloud issues in Slack. Send the issue key, summary, project and issue type from your selected site, optionally restricted by a JQL filter.

How it works

From a new Jira issue to a Slack triage notice

1 Trigger · 1 Action
Jira1 · Trigger

Issue Created

Receive new issue-created events from your selected Jira Cloud site. An optional JQL filter restricts eligible issues; leaving it blank makes new issues from that site eligible.

Slack2 · Action

Notify the issue channel

Post the issue key and summary, project name and issue type as the FastHook bot. Disable mrkdwn and link and media unfurls; descriptions, comments and attachments are not mapped.

The result

A concise issue summary in the team’s triage channel

Example Slack Jira issue notice

New Jira issue EXAMPLE-42: Improve onboarding — Grüße aus München Project: Example Portal Type: Task

Fictional Jira issue. The prepared message contains four issue fields; it does not include an issue URL. Channel members can read the summary regardless of their Jira access.

Before activation

Set up your workflow

  1. Choose the Jira Cloud site and scope

    Connect Jira and select the site using Browse. Optionally set a JQL filter to restrict the eligible projects or issues. Review the wider site scope if you leave the filter empty.

  2. Select the Slack triage channel

    Connect Slack and choose a channel where the FastHook bot can post. Review its membership before exposing issue summaries and retain the plain-text and disabled-preview settings.

  3. Wait for Connected, then create an issue

    Activate and wait for the trigger to show Connected before creating one fictional issue that matches your JQL filter. Verify its key, summary, project and issue type in Slack.

Details and limitations
  • The trigger observes new creations only. Existing issues and issue updates are not imported. This is a one-way notification rather than a task or status synchronization; manual reruns can send another notice.

  • JQL controls eligibility within the selected site. An empty filter leaves new issues from the selected site eligible. Wait for the trigger’s Connected state before testing, and use an issue that matches your chosen filter.

  • The prepared notice is deliberately short. Only key, summary, project name and issue type are mapped. There is no issue-link mapping, description, comment or attachment copy. Slack mrkdwn and automatic link and media previews are disabled.

Questions about this template

Can I restrict notifications to one Jira project?

Yes. Select the Jira Cloud site with Browse and use the optional JQL filter to restrict eligible issues. Without a filter, new issues from the selected site are eligible.

When should I create the test issue?

After activation and once the trigger shows Connected. Create a new fictional issue matching your filter; existing issues and later updates are not imported.

Does the Slack message contain an issue link or description?

No. The prepared text includes the issue key, summary, project name and issue type only. An issue URL, descriptions, comments and attachments are not mapped.

Will changing the Jira status update Slack?

No. This listens for new issue creations and posts a separate notice. It does not synchronize statuses or edit previous Slack messages, and reruns can post duplicates.

Explore connected apps