Congrats - your Jira project is officially friends with Discord! 🎉 Now, let’s set up your first notification rule so everyone stays updated without all the tab-hopping.
Before You Jump In
Make sure you’ve:
- ✅ Connected your Discord server and enabled your project
- ✅ Jira Project Admin rights to configure notifications
- ✅ Jiri bot is happily sitting in your Discord server
💡 Quick note: In Jira, work items are called issues - these could be tasks, bugs, user stories, or epics. Understanding this helps you set up better notification filters!
Step 1: Navigate to Project Notification Settings
- Go to your Jira project settings:
- Open your enabled Jira project
- Click Project Settings → Apps → Discord → General Features
- Look for the Configure Project Notifications section
🚀 Pro tip: You can also navigate here from General Settings by clicking the project link in the Jira Projects list!
- Start creating your notification rule:
- Click Configure Notifications to open the notification rule form
Step 2: Set Up Basic Information
Time to create your first notification rule:
- Name your rule:
- Enter something descriptive like “Bug Alerts” or “Team Updates”
- This is just for your reference - nobody else sees it
Step 3: Configure Where Notifications Go
- Discord server (preselected):
- You’ll see your connected Discord server displayed here
- This is automatically set based on your project’s enabled servers
- Pick your Discord channel:
- Select the channel where Jira updates should appear
- Consider creating a dedicated channel like
#jira-updatesto avoid flooding#general
Step 4: Set Up Notification Triggers
Choose what Jira events should trigger Discord notifications:
- Issue Events:
- Created - When new issues are made
- Updated - Enables field changes and status transition options below (doesn’t trigger notifications by itself)
- Comment Events:
- Created - When someone adds comments
- Field Changes:
- Select specific fields like Summary, Priority, or Assignee
- Only changes to these fields will trigger notifications
- Status Transitions:
- Pick status changes like “To Do → In Progress” or “Done”
💡 Quick tip: Start simple! You can always add more triggers later. Too many notifications can get noisy.
Step 5: Add Filters (Optional but Powerful)
Want to reduce notification spam? Add a JQL filter:
- Common filters:
issuetype = Bug- Only bug notificationspriority = High- Critical issues only
- Leave empty for all project updates (warning: could get chatty!)
🤓 Need JQL help? Check out Atlassian’s JQL Guide for JQL basics, or see our Advanced Notification Guide for more specific Discord for Jira filtering examples.
Step 6: Customize Notification Appearance
Make your Discord notifications more informative:
- Additional fields to display:
- Priority
- Assignee
- Comment Text
- Description
- Due Date
- Sprint
- Select what’s useful for your team - more fields mean longer messages
Step 7: Save and Test
-
Click Create Rule to save your notification setup
-
Test it out:
- Create a test issue in Jira or add a comment
- Check your Discord channel for the notification
- Success? You’re all set! 🎉
Quick Troubleshooting
🤔 Notification not appearing? Make sure the Jiri bot has permission to post in your selected Discord channel.
🤔 Test issue not triggering notification? Check your JQL filter - your test issue might not match the criteria.
Need more help? Check our Troubleshooting & FAQ page or swing by the Discord for Jira Community - we’ve got your back!
What’s Next?
Your notifications are live! Now you can:
- Add More Notification Rules — Set up different rules for different teams
- Configure Bot Permissions — Fine-tune what Jiri can do in your server
Happy Jira-ing! 😄
