Jira

Connect your Jira workspace to Oplix to automatically create and manage issues from bug reports collected through Discord, your game engine, or community feedback. This integration bridges the gap between player-reported bugs and your development workflow.

Prerequisites

Before setting up Jira integration, make sure you have:

Active Oplix Subscription - Navigate to Team Settings > Billing to subscribe
Jira Account - You need access to an Atlassian Jira workspace
Jira Admin Permissions - Required to authorize Oplix to create and manage issues
Team Admin Access - You need admin permissions in your Oplix team

How Jira Integration Works

Once connected, Oplix can automatically push bug reports from Discord or your game directly into your Jira project as issues. You choose which Jira project and issue type to use, and Oplix handles the rest. No more manually copying bug reports from Discord into Jira tickets!

Setting Up Jira Integration

Head to your Team Settings by clicking your profile picture in the top right, then selecting Team Settings. From there, click on the Integrations tab.

Step 1: Enable Jira Integration

Find the Jira Integration card in your integrations list. Click the toggle switch to enable it. The card will expand to reveal the setup form.

Step 2: Name Your Integration

You’ll see a simple form asking for an Integration Name. Give it a descriptive name like “Main Dev Workspace” or “Bug Tracker” - something that makes sense if you end up having multiple Jira integrations down the line.

Type in your chosen name and click Authenticate with Jira. Don’t worry if you’re not sure what to name it - you can always change this later!

Step 3: Authenticate with Atlassian

Clicking the authenticate button will redirect you to Atlassian’s login page. You’ll need to log in with your Jira account credentials if you’re not already logged in.

Atlassian will show you a permission request screen asking if Oplix can access your Jira workspace. You’ll see the specific permissions Oplix needs (like creating issues, reading projects, and managing webhooks). These permissions let Oplix do its job without giving it more access than necessary.

Go ahead and click Accept or Allow to grant these permissions. Atlassian will then redirect you back to Oplix with the connection established.

💡 What Oplix Can Access

Oplix requests read and write access to your Jira workspace, along with webhook management. This allows it to create issues, update them, and receive notifications when things change in Jira. Oplix never deletes your existing issues or modifies anything you didn’t tell it to touch.

Step 4: Confirm Connection

After redirecting back to Oplix, you should see your Jira integration listed as active. The card will show your integration name and the last sync time. You’re now ready to configure how bug reports flow into Jira!

✨ Multiple Jira Workspaces?

If you work with multiple Jira workspaces or want to route different types of reports to different projects, you can set up multiple Jira integrations. Just repeat this process with a different name for each one.

Configuring Bug Report Mapping

Now that Jira is connected, you need to tell Oplix which Jira project and issue type to use when creating bugs. This happens in two places depending on where your bug reports come from:

For Discord Bug Reports

Head to Configuration > Discord in your sidebar. If you haven’t set up Discord yet, you’ll need to do that first. Once Discord is configured:

Navigate to the Integrations section within Discord Configuration
You’ll see your Jira integration listed
Click Configure or Map Channels to set up the connection
Choose which Discord channel’s bugs should go to Jira
Select your Jira Project from the dropdown
Choose the Issue Type (usually “Bug” or “Task”)
Configure any additional field mappings as needed
Click Save

Now when users submit bug reports in that Discord channel, Oplix will automatically create corresponding Jira issues!

For Game Engine Bug Reports

If you’re collecting bugs directly from your game, head to Configuration > Game Engine in your sidebar. Make sure you’ve set up your game engine integration first, then:

Navigate to the Integrations tab within Game Engine Configuration
Find your Jira integration
Click Map App or Configure
Select which game/app’s bugs should sync to Jira
Choose your Jira Project
Select the Issue Type
Configure any custom field mappings
Save your settings

Bug reports submitted from your game will now automatically appear as Jira issues in the project you selected!

✨ Different Projects for Different Sources

You can route Discord bugs to one Jira project and game engine bugs to another. This is great for separating community-reported issues from internal QA testing. Just configure each source independently!

Managing Your Jira Integration

Editing Integration Settings

Need to rename your integration or adjust settings? Click the Settings icon (gear) on your Jira integration card in Team Integrations.

You’ll see your current integration details. Click the Edit button next to the integration name to change it. Update the name and hit the checkmark to save.

Re-authenticating

If your Jira connection expires or you need to switch to a different Jira account, you’ll need to delete the existing integration and set up a new one. Jira OAuth tokens don’t expire often, but it can happen if you change your Atlassian password or revoke access.

Viewing Sync Activity

The integration card shows the Last Synced timestamp, which updates whenever Oplix communicates with Jira. This includes creating new issues, updating existing ones, or checking for changes. If you’re seeing fresh bug reports appear as Jira issues, everything is working correctly!

Removing the Integration

To disconnect Jira, click the Settings icon on the integration card and then click Delete. You’ll see a confirmation dialog warning you this action can’t be undone.

Deleting the Jira integration will:

Stop new bug reports from creating Jira issues
Remove the mapping configurations in Discord and Game Engine
Keep any Jira issues that were already created (Oplix doesn’t delete your existing work)

You can always reconnect later if needed, but you’ll need to reconfigure the project mappings again.

⚠️ Heads Up on Deletion

When you delete a Jira integration, any mapped channels or apps will stop sending bugs to Jira immediately. Make sure your team knows this is happening so they don’t wonder why new bugs aren’t showing up in Jira anymore!

What Happens After Setup

Once Jira integration is configured and mapped to your bug sources:

Automatic Issue Creation - Every qualifying bug report from Discord or your game instantly becomes a Jira issue in the project you specified. No manual copying and pasting required!

Rich Issue Details - The Jira issue includes all the details from the original bug report: description, steps to reproduce, device info, attachments, and more. Everything your developers need is right there in the issue.

Bidirectional Updates - If you update the bug status in Oplix, it syncs to Jira. When developers close the Jira issue, that status can flow back to Oplix (depending on your configuration).

Customizable Mappings - You can configure exactly which custom fields in Jira get populated from bug report data. Map priorities, components, labels, and more to match your team’s workflow.

Common Issues

⚠️ Authentication Failed

If authentication with Atlassian fails:

Make sure you’re logging in with an account that has admin access to the Jira workspace
Check if pop-ups are blocked in your browser (the OAuth flow needs them)
Try using an incognito/private browsing window to rule out cookie issues
Verify your Jira account is active and not suspended

💡 Issues Not Being Created

If bug reports aren’t turning into Jira issues:

Confirm you’ve completed the mapping configuration in Discord or Game Engine settings
Check that the Jira project you selected still exists and you have access to it
Verify the issue type you chose is still available in that project
Make sure your Oplix subscription is active
Look for error messages in the Oplix UI when bug reports are submitted

💡 Can't See My Jira Projects

If the project dropdown is empty when configuring mappings:

Refresh the page and try again
Verify you granted all requested permissions during OAuth
Check that you have at least one project in your Jira workspace
Try disconnecting and reconnecting the integration
Contact support if the problem persists

⚠️ Permission Errors

If you see permission-related errors when creating issues:

Verify your Jira account has permission to create issues in the selected project
Check if the issue type you selected requires special permissions
Make sure you haven’t revoked Oplix’s access in your Atlassian account settings
Try re-authenticating by deleting and re-adding the integration

What’s Next?

Now that your Jira integration is set up and mapped, here are some things to explore:

Configure Discord Channels - If you haven’t already, head to Configuration > Discord to set up which Discord channels send bugs to Jira. You can create dedicated bug report channels with custom forms that map perfectly to your Jira workflow.

Link Your Game Engine - Connect your game to Oplix so players can report bugs directly from within your game. Navigate to Configuration > Game Engine to add the Oplix plugin, then map those reports to Jira.

Customize Field Mappings - Dive into the advanced settings to map custom Jira fields to specific bug report data. You can auto-populate components, priority levels, sprint assignments, and more.

Set Up Trello Too - Want to use both Jira and Trello for different purposes? You can set up multiple project management integrations and route bugs to different tools based on your needs.

Monitor Your Workflow - Check the Dashboard to see analytics on how many bugs are being created, resolved, and their average time to resolution. Oplix gives you visibility into your entire bug management pipeline!

The power of Jira integration really shines when you combine it with Discord and Game Engine bug reporting. Players report issues in natural language, and your development team gets perfectly formatted Jira tickets. It’s automation that actually saves time!