📖 Browse Documentation

Configure Notifications

📋 Before You Start:

  • You have Jira admin or project admin rights
  • You have connected your Discord server in General Settings
  • The target Jira project is enabled for Discord

Ready for advanced control? This guide walks through every section of a notification rule (in the same order and names as the UI), including new options from the redesign. If you're just getting started, see Configure First Notifications.

🛡️ Admin tip: You can create and manage rules from the Global Settings page to cover many projects at once. Use All Enabled Projects for instance-wide rules; create project-specific rules for exceptions.

Basic Information

  • Rule name: Only used for identification.

What to Monitor

  • Select project: Choose a single project or pick All Enabled Projects.
  • JQL filter: Narrow which issues can trigger this rule. Test your JQL in Jira first.

💡 Quick tip: Keep JQL simple at first (e.g., issuetype = Bug), then refine.

Looking for examples and recipes? See JQL Filters for Notifications.

Where to Send

  • Discord Server and Discord destination: Where notifications are sent.
    • Channels that Jiri cannot currently use remain visible with Needs access. Select one to see the exact missing Discord permissions, fix them in Discord, then select Recheck permissions.
    • Ordinary channel notifications require View Channel, Send Messages, and Embed Links.
    • Attach Files is also required when an active issue or comment notification includes project artwork, attachments, descriptions, or comment text that can contain files.
  • Advanced Delivery Options:
    • Send notifications to Discord threads: Optional setting (default: Off) that keeps channels tidy by posting follow-up updates inside an issue‑named thread.
      • Thread delivery requires View Channel, Create Public Threads, Send Messages in Threads, and Embed Links. Attach Files is added only when the configured content can produce files. The channel warning updates when you change either delivery mode or content.

💬 Learn more: See Discuss Jira Issues on Discord for manual threads and auto-threads behavior.

  • Additional Discord role mentions: Always mention selected roles on messages.

When to Notify

  • Issue is: Select events (Created, Updated).
  • Comment is: Select events (Created).
  • Advanced trigger options: Extra conditions for when to fire.
  • Field changes: Only notify when specific fields change (e.g., 📝 Summary, 🎯 Priority, 🙋 Assignee, 🔄 Status).
  • Status transitions: Only notify for selected status changes.
  • Enable bulk update notifications (default: Off): When disabled, Jira bulk update webhooks are skipped for this rule. In Forge, Atlassian issue events do not identify Jira bulk edits, so this setting is unavailable and bulk edits can still send notifications.

Message Content

Configure what’s included in Discord messages.

Fields to display in issue notifications (full list)

  • For Jira Software projects:
    • 📦 Issue Type
    • 🔄 Status
    • 🙋 Assignee
    • 🕵️‍♂️ Reporter
    • 🔗 Parent Issue
    • 📋 Project
    • 🏃‍♂️ Sprint
    • 📅 Due Date
    • 🛠️ Fix Versions
    • 🧩 Components
    • 🏷️ Labels
    • 📎 Attachments
    • 🎯 Priority
    • ✏️ Description
  • Additional fields for Jira Service Management projects:
    • 🎫 Request Type
    • 🧵 Ticket Thread

Fields to display in comment notifications

  • For Jira Software projects:
    • 💬 Comment Text
    • 📋 Project
    • 📎 Attachments
  • Additional field for Jira Service Management projects:
    • 🧵 Ticket Thread

Formatting Options

  • Show images in notifications (default: On): Display inline images when available.
  • Show only changed fields (default: On): Only list fields whose values actually changed. Per‑rule toggle.
  • Mention Discord users when mentioned in Jira (default: On): Convert Jira @mentions to Discord pings for connected users.
    • Requires users to have linked their Discord and Jira accounts; unlinked users won’t be pinged.
  • Show change type emojis (default: On): Add visual emojis in titles for changes (e.g., 📝 summary, 🎯 priority, 🙋 assignee, 🔄 status).

Quick Actions (optional)

Add buttons to act directly from Discord messages.

  • Software projects: 💬 Add Comment, 🙋 Assign to me, 🔄 Change Status.
  • Service Management: 🗨️ Reply to Customer, 💬 Add Internal Comment, 🙋 Assign to me, 🔄 Change Status.

Comment action buttons:

  • Software projects: 💬 Reply.
  • Service Management: 🗨️ Reply to Customer, 💬 Add Internal Comment.

📚 See the dedicated guide: Work with Issues for details and required permissions.

🔐 Actions run as the clicking user and require their Jira permissions (Assign Issues, Add Comments, Transition Issues; plus Service Management comment permissions where applicable).

Manage Rules

  • On the notifications list, click the ⋯ (three dots) menu next to a rule to:
    • Duplicate a rule to reuse configuration.
    • Enable/Disable a rule without deleting it.
    • Delete to remove it.
  • The list shows each rule as Active, Disabled, or Paused.
  • A rule is paused when Jiri can no longer access its server or channel, or lacks a permission required by its selected channel or thread delivery mode.
  • Fix the shown Discord configuration problem, then select Try again. The rule resumes only after Jiri verifies the destination and permissions.
  • Saving a corrected paused rule also checks and resumes it.

Discord for Jira sends one concise service email when a rule first pauses, if the Jira site contact is available. The email links back to the affected rule and includes an unsubscribe option for configuration warnings.

Tips to Keep Noise Low

  • Start with a few triggers and fields.
  • Prefer “Show only changed fields” for update-heavy projects.
  • Use role mentions sparingly.

🔍 Field visibility: A field will show only if it exists on the issue type and your Jira permissions allow viewing it.

Have questions? Join our Community.