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.
Quick Checklist (Before You Start)
Make sure youāve:
- ā Connected your Jira project to your Discord server.
- ā Jira Project Admin rights. Hereās how to verify.
- ā Jiri bot is happily sitting in your Discord server.
All good? Awesome, letās get going!
Understanding Jira Issues
In Jira, tasks are collectively called issues. An issue could represent different types of work, including:
- Tasks (general to-dos)
- Bugs (issues to be fixed)
- User Stories (commonly used in Scrum to describe functionality from a user perspective)
- Epics (large bodies of work broken down into smaller issues)
Understanding this helps you configure notifications more effectively!
Step 1: Open Your Discord Integration Settings
- Head to your Jira project.
- Click the three dots (ā¦) next to your projectās name and select Project settings.
- Under Apps, select Discord.
Step 2: Add a Discord Channel for Notifications
- Click Configure Notifications (yep, thatās the magic button).
- Youāll see a form for creating a new notification rule - donāt panic, itās simple.
Step 3: Set Up Your Notification Rule
Hereās what youāll fill out:
- Name your rule: Something descriptive (like āBug Alertsā or āAll Things Jiraā). Nobody else will see this; itās just for your sanity.
- Choose your Discord Channel: Pick the Discord channel that should get Jira updates. (Pro tip: make a dedicated channel so Jira updates donāt flood #general.)
Pick What Jira Updates Trigger Notifications
Time to decide how chatty Jira gets in Discord:
- Issue Events: Select which Jira events send notifications:
- Issue Created or Updated
- Comments Added
- Status changes (e.g., issues moving to āDoneā, āIn Progressā, or any status your workflow loves).
- Specific field changes (like Priority or Assignee).
š” Quick tip: Keep it focused to avoid noise. You can always add more rules later!
Use Filters (JQL) - Optional but Awesome
Want less spam? Add a JQL filter! Examples:
issuetype = Bug(Only bug updates)priority = High(Critical stuff only)- Leave blank for all project updates (fair warning: your Discord could get noisy!)
š¤ Pro tip: Atlassianās JQL Guide can help craft the perfect filter.
Customize Your Notifications (optional)
Want more details in your Discord messages? No problem - select optional fields like:
- Assignee
- Priority
- Due Date
- Components
Step 4: Save & Test Your Setup
- Click Save, and voilĆ - your first notification rule is active!
šØ Quick test: Go create a test issue or add a comment in Jira. Check Discord to see your new notification appear.
Did the notification appear? Great job - you nailed it! If not, donāt panic:
- Ensure your Jiri bot has permissions to post in your Discord channel.
- Double-check your JQL filters (maybe your test issue didnāt match?).
Happy Jira-ing! š
Still no luck? Hop over to our Troubleshooting & FAQ page or swing by the Discord for Jira Community - weāve got your back.
