Ever wish your Jira tickets could magically grab details from Discord without extra work? 🧙♂️ No more wishing - let’s auto-populate those fields and save your sanity (and clicks).
Quick Overview: What You’ll Achieve
When someone creates a Jira issue straight from Discord, wouldn’t it be nice if Jira automatically captured handy Discord details like usernames, server IDs, or links to conversations? Yep, totally possible - and not too tricky either!
By the end of this guide, your Jira tickets will automatically include:
- Discord usernames (no more “who reported this?!”)
- Direct links to the Discord conversations where tickets were born
- Any other Discord details you fancy
Ready? Let’s roll! 🚀
Step 1: Create Custom Jira Fields
First, let’s prep Jira to store all this cool Discord info. You’ll need to create these custom fields manually:
- Discord User Name:
Text Field (single line) - Discord Thread Link:
URL Field
To add these fields, follow the instructions in the “Adding Custom Fields” section of the Configure Ticket Types and Fields guide.
Step 2: Add Fields to Your Request Types
Quick pit stop - make sure these custom fields are visible in your Jira request types, or they’ll stay hidden from your agents (and that defeats the whole purpose!).
- Navigate to Project settings → Request management → Request types in your Jira project.
- Choose the relevant request type and click the Issue view tab.
- Add your new Discord fields to the Description fields or Context fields sections.
For more details, refer to the Configure Ticket Types and Fields guide.
Available Discord Properties
When a ticket is created from Discord, the following properties are available for use in your automation rules:
{
"discord-for-jira-discord-server-id": "The Discord server ID where the ticket was created",
"discord-for-jira-discord-channel-id": "The Discord support channel ID under which the ticket thread was created",
"discord-for-jira-discord-thread-id": "The Discord ticket thread ID",
"discord-for-jira-discord-user-id": "The Discord user ID of the person who created the ticket",
"discord-for-jira-discord-user-name": "The Discord username of the person who created the ticket"
}
Step 3: Set Up Jira Automation
Here’s where the magic 🪄 happens - let’s automate field population.
- Head over to Project Settings → Automation → Create rule.
- Give your automation a friendly name like “Auto-fill Discord Details”.
Automation Breakdown:
-
Trigger: Select
Issue created(because, duh, that’s when you want fields filled!). -
Condition: Add a Compare two values condition:
First value: {{issue.properties.discord-for-jira-discord-thread-id.value}}
Condition: does not equal
Second value: Empty
This ensures the rule only runs when tickets originate from Discord.
- Action: Use the
Edit issueaction and set your fields with these smart values:
- Discord User Name:
{{issue.properties.discord-for-jira-discord-user-name.value}}
- Discord Thread Link:
https://discord.com/channels/{{issue.properties.discord-for-jira-discord-server-id.value}}/{{issue.properties.discord-for-jira-discord-thread-id.value}}
🎯 Pro tip: Copy-paste smart values exactly - typos are automation kryptonite.
Step 4: Test Your Magic 🧪
Let’s see if your new automation rule plays nicely:
- Create an issue from Discord (use
/createor your Ticket Panel). - Hop back into Jira - did your custom fields fill themselves? Awesome! 🎉
If something seems off:
- Check your automation rule’s audit logs for clues.
- Double-check your smart values - remember, no sneaky typos!
FAQ & Troubleshooting
🤔 Fields aren’t populating?
- Verify the custom fields are on the request type’s issue view.
⚠️ Automation not running?
- Check your condition - does the Discord property exist?
- Make sure Jira Automation isn’t paused (yes, that happens!).
Still stuck? Pop into our Discord for Jira Community - we love solving mysteries (and chatting with you!).
Conclusion
By using Jira automation with Discord custom fields, you can capture important context about who created the ticket and where the conversation started. This context opens the door to plenty of possibilities, including:
- Setting additional Jira fields based on Discord info.
- Triggering custom notifications or alerts.
🎯 Pro tip: Pair these automation rules with other Jira Automation capabilities to build even more powerful workflows, making life easier for your support teams and improving reporting accuracy.
Happy automating! ⚙️
