Got the basics of notifications down but want more fine-grained control? You’re in the right place! 🎯 Let’s explore advanced options to keep your Discord notifications tidy, relevant, and spam-free.
💡 Note: If you’re new to notifications, check out Configuring Your First Notifications first.
🔍 Supercharge Notifications with JQL
Ever feel Jira updates are drowning your Discord channels? Enter Jira Query Language (JQL) - your secret weapon for filtering notifications to just the juicy bits.
Here’s how you can use JQL filters to customize your Discord alerts:
🚨 High Priority Only
Want only urgent stuff hitting Discord?
- Filter:
priority in (Highest, High)
🐞 Bugs Only, Please
If your team is laser-focused on bugs:
- Filter:
issuetype = Bug
🎯 Track Specific Labels
Love labels? So does Jiri:
- Filter:
labels in ("frontend", "urgent")
🚦 Status Updates
Track specific status updates easily:
- Filter:
status = "In Progress"
🛠️ Monitor Components
Narrow down by Jira components:
- Filter:
component = "Backend"
📅 Sprint Focus
Keep eyes on the current sprint:
- Filter:
Sprint in openSprints()
👤 Assigned Issues
Only issues assigned to specific teammates:
- Filter:
assignee = "john.doe"
✨ Combine for Power!
Stack filters to refine your results:
- Filter Example:
priority in (Highest, High) AND issuetype = Bug
✅ Test Before You Trust
Always test your filter before using it in Discord. Here’s how:
- In Jira, navigate to Filters → Search issues.
- Switch to JQL mode (there’s a handy button for this).
- Enter your JQL filter and click Search.
⚠️ Note: Jira recently updated its interface, so your UI might look slightly different from the screenshots provided.
If the issues look good - you’re all set! 🚀
📝 Customizing Notification Details
By default, notifications include basic info (summary, issue type, assignee). Want more details?
You can optionally add:
- Priority
- Due Date
- Components
- Snippet of issue descriptions (coming soon!)
🚧 Avoiding Notification Spam
Nobody likes notification overload - least of all your team. A few tips:
- Don’t trigger on every minor update; stick to important status or field changes.
- Regularly review your rules - refine or remove those not adding value.
- Keep Discord channels dedicated. (Your #general will thank you!)
📌 Pro tip: Name your notification rules clearly, so future you won’t curse present you.
🤔 Quick JQL Reference
| What you want | Your JQL |
|---|---|
| High priority issues | priority in (Highest, High) |
| New unresolved bugs | issuetype = Bug AND resolution = Unresolved |
| Issues assigned to a specific person | assignee = "john.doe" |
| Issues currently in progress | status = "In Progress" |
| Customer-reported labeled issues | labels in ("customer") |
📖 JQL Help Needed?
Feeling adventurous? Atlassian’s JQL documentation has got you covered.
❓ Still Have Questions?
Hop into our friendly Discord for Jira Community. We chat, we laugh, we troubleshoot - come join us!
