What's New

• Channel and thread notifications now keep delivering text, links, actions, mentions, and externally hosted media when Jiri lacks Attach Files
• Local Jira uploads and generated project artwork are safely omitted, and Jira shows Active · attachments skipped only after content was skipped
• Admins can open the permission guide directly from the active warning; granting Attach Files restores upload-backed content

• Issue and comment notifications now show the Jira issue type when Jira does not provide Request Type details

• Issue update notifications and Ticket Automation can now recover from brief Jira project-loading failures

• New ticket notification cards that include Ticket Thread now show the actual thread link when Discord finishes creating the thread just after Jira creates the issue

• Connecting Jiri or a Discord account from Jira now continues directly to Discord without an extra external-site warning

• New Jira comment notifications now recover when Jira briefly delays making the comment readable

• Fixed cases where Jira sites needed manual support to finish setting up or updating Discord for Jira

• When Jira Service Management product access is missing, Ticket Automation now lists the app-user groups an admin can restore with the User (agent) role and links to the permissions guide
• Discord ticket reporters receive a concise unavailable message while recovery details remain in Jira for administrators

• Jira comment notifications with many text and media sections now continue sending to Discord

• When Discord omits a channel that Jiri cannot view, a saved destination remains selected as Unavailable so admins can restore access or choose another channel
• Visible channels that need other permissions continue to show Needs access with the exact permissions to fix

• Project admins can now open one Discord page in Jira project settings, with General Features and Ticket Automation available as tabs inside it

• Fixed cases where the Discord discussion panel did not open automatically for a new Jira issue

• Issue panels and ticket commands now provide clearer guidance when Jira content or access is unavailable

• Fixed sprint links in notifications for Scrum boards and boards shared across Jira projects

• Channel pickers now keep inaccessible destinations visible with Needs access and show the exact missing Discord permissions before saving, creating, or linking
• After fixing permissions in Discord, users can recheck access directly from Jira

• Notifications are now more reliable during brief Jira service interruptions

• Improved notification processing during large Jira update bursts
• Due-date changes continue sending when Jira provides an unexpected changelog value

• Existing Jira links and bookmarks now continue to open the correct Discord for Jira settings page after upgrading to the Forge app
• Connecting a Discord account from Personal Settings now moves an existing connection without moving another Jira account's personal notification rules

• Discord notifications now keep sending when a Jira comment contains an external image link that is too long for Discord

• Channel and personal notification rules now pause after a confirmed Discord configuration problem instead of failing repeatedly
• Jira shows the affected rules, exact reason, and a live Try again action
• Affected users or site contacts can receive one concise service email with recovery instructions and a separate unsubscribe option

• Fixed Jira @mentions in comments and issue descriptions so connected users are tagged correctly in Discord notifications

• Ticket settings now let admins decide whether a Jira assignee is automatically added to the Discord ticket discussion
• Teams can keep Jira auto-assignment enabled without exposing the assigned support agent in Discord until they manually join

• Ticket automation now supports Discord forum channels as destinations, not just text channels
• Creating a ticket from a message inside the configured forum now reuses that same forum post as the ticket discussion
• Sending a ticket panel to a forum now creates a dedicated forum post that contains the panel
• Ticket permission guidance now distinguishes forum requirements from text-channel thread requirements

• The "Assign to me" button now uses Jira's dedicated assignee API endpoint for more reliable assignment updates
• Assignment failures now show clearer user-friendly messages in Discord while detailed Jira errors stay in logs
• Assign action configuration no longer shows pre-check permission warnings because action permissions are evaluated per user at click time

• The Jira Discord panel now shows clear messages when a thread is deleted, the server is removed, or the bot lacks access
• Issue panels no longer fail to load when a linked Discord server is unavailable

• New installations now receive a one-time welcome email sent to the billing or technical contact from Marketplace
• The email includes setup links for notifications and ticket panels plus an unsubscribe option for onboarding emails

• Long attachment filenames are now shortened automatically so Discord cards with file attachments send reliably
• Jiri Support now has its own ticket-focused install landing page with clearer setup links

• Notification rules can now suppress Jira bulk update webhooks to reduce channel noise

• Fixed an issue where Jira panels did not load in some scenarios
• Jira now shows a clear error for users that are not members of the Discord server when they try to create a discussion thread
• The "Manage Discord servers" shortcut in project settings now shows only for Jira admins
• Ticket close messages now keep archived Discord threads closed instead of reopening them

• Ticket panels now warn admins when a configured request type no longer exists in Jira
• Users get a clear message if they click a removed ticket type from a panel
• Notifications are more reliable during temporary Jira outages or API slowdowns due to added retries

• Ticket thread starter cards now use the Discord components v2 layout
• Short fields show aligned label/value rows, while long text fields show labels above the value
• Attachments uploaded during ticket creation now appear directly in the ticket thread card

• Select and multi-select fields now render as Discord dropdowns in ticket creation forms
• Selections are prefilled when AI suggestions match available options
• Fields with too many options fall back to text input for full coverage
• Labels fields are now supported with comma-separated input
• Attachments are now supported in ticket modals
• Date fields accept YYYY-MM-DD in the Discord ticket modal
• Number fields accept integers and decimals

Configuration page improvements

• Field dropdowns include type emojis for faster scanning
• Unsupported fields show a clear "Unsupported" badge in the picker
• Ticket type lists show emojis, with a fallback when none is configured

• Link existing channel threads and forum posts to Jira issues or tickets
• Channels with insufficient permissions are now marked in the channel picker
• Default thread names now include the Jira issue title

• Jira info, note, warning, error, and success panels are now displayed in Discord notifications with proper formatting

• Select custom fields to be displayed on notification cards
• Currently supports single-select fields

• Custom fields can now be included when creating issues from Discord
• Currently supports single-select fields (more field types coming soon)

• Messages that contain attachments but no text are now displayed correctly in Jira issues
• Message timestamps are now friendlier ("16 minutes ago" instead of "Aug 26, 2025")
• Consecutive messages from the same user are grouped when posted less than 7 minutes apart (matches Discord)

• New "Ticket Thread" selectable field for notification cards for quick navigation to the ticket thread
• "Add Comment" button renamed to "Add Internal Comment" for clarity
• Comment messages now include a link to the original Discord message and the reporter's Discord profile

• Replaced direct Jira links with a "More Info" button in Discord threads
• Ticket reporters see a link to the Discord thread, support team sees the Jira ticket link
• Ticket status is now displayed for quick progress visibility

• After creating a ticket in Discord, a direct link to the Jira issue is now displayed

• New Discord-related issue properties for capturing Discord user details, channel/thread info
• Enables smoother support workflows and deeper reporting

• Assign a Discord role to each request type
• Role is automatically added to new ticket threads for instant notifications

• Two additional standard fields (Priority and Components) now supported
• Issue preview displayed immediately after creation, showing missing priority and assignee details
• New ticket configurations prefilled with all available request types for faster setup
• Layout improvements for project and ticket configuration pages (more visible content, less scrolling)
• Unsupported request type fields now visible and labeled in the configuration modal
• Improved error messages when request type is not found or when unsupported fields are selected