Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Configuring Slack Integration

Within Jira, users can configure notifications to post based on particular events (e.g. commenting, issue creation, etc). To do so:

  1. Navigate to the project in question
  2. Click Project Settings
  3. Click Slack Integration
  4. If you have not yet linked Jira and Slack, click "Confirm access to your Slack account"
  5. Click the dropdown to select the channel into which notifications will be posted, and click Add
  6. Select the types of actions that you would like to be alerted on
  7. By default, all issues in the project will trigger a notification. If desired, you can filter which events trigger the messages by clicking Advanced, and providing a JQL filter


Creating Email Subscriptions

You can configure the results of a filter query to be sent via email to one or more users using the following steps:


  1. Navigate to an existing filter that you would like
  2. If one does not exist:
    1. Click Issues → Search For Issues
    2. Enter the JQL and click Search
    3. Click Save as
    4. Provide a name for the filter (note that this name will appear in the email notification) and click Save
  3. Click Details → New Subscription
  4. From the Recipients dropdown, select who should receive the email (Personal Subscription will send just to you)
  5. Select when you'd like the report to be sent via the Schedule and Interval options
  6. By default, Jira will not send an email if the filter contains no results. Check the box to always send the notification, even if there are no results
  7. Click Subscribe
  8. To modify the subscribers, click Details → Manage Subscriptions. From there, you can edit, delete, and perform an ad-hoc run of the existing reports


Note: While you can send a filter subscription to anyone, note that if a user attempts to click on an issue link in the emial that they receive, they must have access to Jira and the project itself (unless it is public) in order to retrieve the details.



On this page:

  • No labels