6.7 KiB

Raw Permalink Blame History

JIRA AI Fixer - User Guide

What is JIRA AI Fixer?

JIRA AI Fixer is an AI-powered system that automatically analyzes support tickets from your issue tracking system, identifies the root cause in your codebase, and creates pull requests with suggested fixes.

Supported Platforms

Platform	Status	Webhook Endpoint
TicketHub	✅ Active	`/api/webhook/tickethub`
JIRA	✅ Ready	`/api/webhook/jira`
ServiceNow	✅ Ready	`/api/webhook/servicenow`
Zendesk	✅ Ready	`/api/webhook/zendesk`
Azure DevOps	✅ Ready	`/api/webhook/azure-devops`
GitHub Issues	✅ Ready	`/api/webhook/github`
GitLab Issues	✅ Ready	`/api/webhook/gitlab`
Custom Systems	✅ Ready	`/api/webhook/generic`

How It Works

1. Ticket Created → 2. Webhook Sent → 3. AI Analyzes → 4. PR Created → 5. Result Posted
     (JIRA)           (automatic)      (30 seconds)      (Gitea)        (back to JIRA)

Step-by-Step Flow

Ticket Created: A support ticket is created in your issue tracker (JIRA, ServiceNow, etc.)
Webhook Triggered: Your issue tracker sends a webhook to JIRA AI Fixer
AI Analysis: The system:
- Fetches relevant source code from your repositories
- Sends the ticket description + code to an AI model
- Identifies root cause and affected files
- Generates a fix suggestion
PR Created: If a fix is found:
- Creates a new branch (fix/TICKET-123-auto-fix)
- Applies the code change
- Opens a Pull Request with full explanation
Result Posted: A comment is added to your original ticket with:
- Root cause analysis
- Affected files
- Suggested fix
- Link to the Pull Request
- Confidence score

Setting Up Webhooks

JIRA

Go to Settings → System → Webhooks
Click Create a Webhook
Set URL: https://jira-fixer.startdata.com.br/api/webhook/jira
Events: Select Issue → created
Save

ServiceNow

Go to System Web Services → Outbound → REST Message
Create new REST Message pointing to: https://jira-fixer.startdata.com.br/api/webhook/servicenow
Create a Business Rule on Incident table to trigger on Insert

Zendesk

Go to Admin Center → Apps and integrations → Webhooks
Create webhook with endpoint: https://jira-fixer.startdata.com.br/api/webhook/zendesk
Create Trigger: When ticket is created → Notify webhook

Azure DevOps

Go to Project Settings → Service hooks
Create subscription for Work item created
Set URL: https://jira-fixer.startdata.com.br/api/webhook/azure-devops

GitHub

Go to Repository → Settings → Webhooks
Add webhook: https://jira-fixer.startdata.com.br/api/webhook/github
Select events: Issues
Content type: application/json

GitLab

Go to Settings → Webhooks
URL: https://jira-fixer.startdata.com.br/api/webhook/gitlab
Trigger: Issues events

Custom System (Generic)

Send a POST request with this format:

{
  "id": "your-ticket-id",
  "key": "PROJ-123",
  "title": "Issue title",
  "description": "Detailed description of the problem",
  "source": "your-system-name",
  "priority": "high",
  "labels": ["bug", "production"],
  "callback_url": "https://your-system.com/api/tickets/123/comments"
}

Dashboard

Access the dashboard at: https://jira-fixer.startdata.com.br

Features

Real-time Statistics: Total issues, analyzed, PRs created, average confidence
Issue List: View all processed issues with status
Issue Detail: Click any issue to see full analysis, suggested fix, and PR link
Filter by Source: Filter issues by origin system (JIRA, ServiceNow, etc.)
Filter by Status: Filter by pending, analyzed, or error

Understanding Results

Analysis Comment Format

When analysis completes, you'll see a comment like this:

🤖 AI ANALYSIS COMPLETE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📋 ROOT CAUSE:
The WS-AVAILABLE-BALANCE field is declared as PIC 9(9)V99 which can only
hold values up to 9,999,999.99. Values above this are truncated.

📁 AFFECTED FILES: AUTH.CBL

🔧 SUGGESTED FIX:
────────────────────────────────────────
Change line 15 from:
  05  WS-AVAILABLE-BALANCE   PIC 9(9)V99.
To:
  05  WS-AVAILABLE-BALANCE   PIC 9(11)V99.
────────────────────────────────────────

🔀 PULL REQUEST CREATED:
────────────────────────────────────────
Branch: fix/supp-1-auto-fix
PR: #5
URL: https://gitea.startdata.com.br/startdata/cobol-sample-app/pulls/5
────────────────────────────────────────

📊 CONFIDENCE: 92%

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Analyzed by JIRA AI Fixer

Confidence Score

Score	Meaning
90-100%	Very likely correct - review and merge
70-89%	Probably correct - review carefully
50-69%	Uncertain - manual investigation recommended
<50%	Low confidence - use as a starting point only

Best Practices

Writing Good Ticket Descriptions

The AI works best with detailed descriptions:

Good:

Transaction auth failing for amounts over $10 million.
- Error: "Insufficient funds" even when balance is adequate
- Affected accounts: Corporate accounts with high limits
- Started after last month's release
- Error code: AUTH-5012

Poor:

auth broken

Reviewing PRs

Always review AI-generated PRs before merging
Run your test suite on the fix branch
Check if the analysis matches your understanding
Look for edge cases the AI might have missed

Troubleshooting

Issue Not Analyzed

Check webhook delivery in your issue tracker
Verify the endpoint URL is correct
Check the JIRA AI Fixer dashboard for errors

Low Confidence Scores

Provide more detail in ticket descriptions
Ensure relevant code is in indexed repositories
Check if the issue type is supported

PR Not Created

Repository must be connected to Gitea
Code must be in indexed directory
Fix must be auto-applicable (simple changes work best)

Contact

Dashboard: https://jira-fixer.startdata.com.br
Portal: https://aifixerportal.startdata.com.br
Support: support@startdata.com.br

JIRA AI Fixer - Intelligent Support Case Resolution Created by StartData

6.7 KiB Raw Permalink Blame History