Your agency uses Jira to manage projects. Your clients use your WordPress site. Asking clients to file Jira tickets directly is a non-starter — they will not create an account, learn the interface, or fill in the right fields. So bugs get reported via email, Slack DMs, and phone calls. Context is lost. Time is wasted.
BugPost fixes this by letting clients report bugs directly on the site, then automatically creating Jira issues with full technical context. Your clients click a button. Your developers get a structured Jira ticket.
Why Jira for WordPress Bug Tracking
Jira is the standard for teams that need structured project management. If your agency already runs sprints, backlogs, and epics in Jira, adding client-reported bugs to that same system makes sense:
- Single source of truth. All work — internal and client-reported — lives in Jira.
- Existing workflows. You already have boards, filters, and automation rules. Client bugs slot right in.
- Assignment and scheduling. Assign the issue to a developer, add it to a sprint, set a due date — all the things Jira already does well.
- Two-way sync. Status changes in Jira update the report in WordPress. Your client support team sees the current state without leaving WP admin.
What You Need
- An Atlassian account (the free Jira tier supports up to 10 users)
- A Jira Cloud project
- BugPost Pro installed and activated
Step-by-Step Setup
Step 1: Create a Jira API Token
1. Go to id.atlassian.com/manage-profile/security/api-tokens.
2. Click Create API token.
3. Give it a label like "BugPost" and click Create.
4. Copy the token immediately — Atlassian will not show it again.
Step 2: Find Your Jira Details
Base URL: Your Jira Cloud URL, e.g., https://yourcompany.atlassian.net (no trailing slash).
Project Key: The short code for your project, visible in issue numbers. If your issues are labeled PROJ-1, PROJ-2, the key is PROJ. Find it in Project Settings → Details.
Issue Type: Usually Bug. Check your project's issue types if you use a custom scheme.
Step 3: Connect BugPost to Jira
1. In WordPress admin, go to BugPost → Settings.
2. Scroll to Jira Integration.
3. Enter your Atlassian email (the one tied to your Atlassian account).
4. Paste the API Token.
5. Enter the Base URL and Project Key.
6. Click Test Jira Connection. You should see: "Connected as [Your Name] ([email])."
Step 4: Enable Auto-Create
Check Automatically create a Jira issue for every new bug report and click Save Settings.
Step 5: Set Up Two-Way Sync (Optional)
1. In Jira, go to Settings → System → WebHooks (or search for "WebHooks" in Jira settings).
2. Click Create a WebHook.
3. Name it "BugPost" and paste the Webhook URL shown in your BugPost Jira settings.
4. Paste the Webhook Secret from BugPost into the secret field.
5. Under events, enable Issue: updated.
6. Save.
Important: The webhook secret is auto-generated by BugPost. It is not the same as your API token. Never use your API token as a webhook secret.
What the Jira Issue Looks Like
When a bug report is submitted, the auto-created Jira issue includes:
- Summary: The bug report title (category + page)
- Description: The reporter's comment, followed by structured context — page URL, browser, OS, viewport size, console errors
- Issue Type: Bug (or whatever you configured)
- Link back: URL to the full report in your WordPress admin
Your developers get everything they need to start working without asking a single follow-up question.
Two-Way Sync Behavior
- Resolve the issue in Jira → report status in WordPress updates to "Resolved"
- Close the issue in Jira → report status updates to "Closed"
- Move the report to "In Progress" in WordPress (Kanban board) → Jira issue transitions accordingly
Tips for Agencies
Create a dedicated project for client bugs
Keep client-reported bugs separate from internal development issues. Create a project called "Client Bugs" with a key like CBUG. This prevents client reports from cluttering your development backlog while still giving them full Jira workflow support.
Use Jira automation rules
Jira's built-in automation can auto-assign new issues to a team lead, add them to the current sprint, or send a Slack notification. Set up a rule like: "When issue created in CBUG project → assign to [QA lead] → add to current sprint."
You do not need auto-create for every report
If you prefer to triage before escalating, leave auto-create off. Each report in your WordPress admin has a "Create Jira Issue" button that lets you send specific reports to Jira on demand.
Stop Copy-Pasting Bug Reports into Jira
BugPost Pro auto-creates Jira issues with full context from client-submitted bug reports. Two-way sync keeps everything current.
See Pricing