TL;DR - Iโve released a massive Discord for Jira notifications redesign throughout July: added oneโclick actions, auto-threads by issue, expanded fields (5โ16+), better formatting, Discord mentions, visual emojis, duplicating/disabling notification rules, and global notifications. Quite a lot ๐
Oneโclick actions
Finally, you can work end-to-end on Jira issues without leaving Discord. Each notification card now adds quick action buttons:
For regular Jira projects:
- ๐ฌ Add comment
- ๐ Assign to me
- ๐ Change status (multiple buttons, one for each available status transition)
For Service Desk projects:
- ๐ฌ Reply to customer
- ๐ Add internal comment
- ๐ Assign to me
- ๐ Change status
With these, you can claim a ticket or issue, leave a short comment, and move status without switching tabs. Personally, I use them all the time now. Not that I donโt like Jira for it, itโs just much faster and more convenient from Discord.
Notification threads by issue
When the first message about TASK-123
appears, the bot opens a thread named after the ticket. Later updates for that task go into the same thread.
- Notifications and related issue discussions stay grouped by Jira issue
- Main channel remains readable (less noise)
- You can review an issueโs history with one click instead of scrolling
Expanded field support
Previously, Discord for Jira only supported displaying 5 basic fields: summary, description, priority, sprint, and due date. Now you can choose from 16+ fields including:
- ๐ฆ Issue Type, ๐ Status, ๐ Assignee, ๐ต๏ธโโ๏ธ Reporter
- ๐ Parent Issue, ๐ Project, ๐โโ๏ธ Sprint, ๐ Due Date
- ๐ ๏ธ Fix Versions, ๐งฉ Components, ๐ท๏ธ Labels, ๐ Attachments
- ๐ซ Request Type and ๐งต Ticket Thread (for Service Desk projects)
This means you can now see the complete picture of any Jira issue directly in Discord, with all the context you need to make decisions without switching to Jira.
Improved notification formatting
Previous notifications struggled with formatting lists, code blocks, and inline images. The new renderer now supports:
- Nested bullet and ordered lists
- Basic text styles (bold, italic, strike, underline, inline code)
- Fenced code blocks with syntax highlighting
- Quote blocks
- Clean links
- Inline images, GIFs, and video
If you write long specs or bug reports, you can now review them inside Discord without losing structure. Whatโs especially helpful is that now both images and attachments are being displayed in Discord, so you donโt need to open Jira to see them now.
Show only changed fields
Big issues and tickets may track dozens of fields. You probably donโt need all of them every time someone tweaks a label.
Turn on Show only changed fields and the bot lists only what is different between the previous and new values.
Discord mentions integration
Two new options make notifications more interactive and ensure the right people get notified:
Automatic Discord mentions: The bot can now automatically replace Jira mentions and user names with Discord mentions that will ping mentioned users in Discord. When someone is mentioned in a Jira comment or description, theyโll get a proper Discord notification.
Additional Discord role mentions: You can configure notifications to mention additional Discord roles, ensuring specific teams or groups are always notified about relevant issues.
Visual notification improvements
Optional emojis in notification titles: To make different types of notifications more visually distinct, you can now turn on showing change type emojis. When enabled, action messages will include emojis that indicate the type of change:
- ๐ Summary changes
- ๐ฏ Priority updates
- ๐ Assignee changes
- ๐ Status transitions
- And many more for different field types
This makes it much easier to quickly scan through notifications and understand what changed at a glance.
Useful notification rule actions
Duplicating notification rules: You can now duplicate existing notification rules, making it much faster to set up similar rules across different projects or with slight variations.
Enable/disable notifications: Toggle notification rules on and off without deleting them. Perfect for temporarily disabling notifications during maintenance or testing periods.
Global notifications
Admins can create global notification rules, instead of creating a separate rule in each enabled Jira project.
I had a lot of fun implementing all these improvements! My goal is to make these Discord notifications not only as useful as possible by making them beautiful, relevant, organized, and targeting the right people, but also making them interactive with quick actions, so you can work with Jira tasks without ever leaving Discord.