Feature-Request-Workflow:
  
Kunde: "Könnten Sie eine Integration zu Salesforce hinzufügen?"

KI: "Das ist eine großartige Idee! Ich dokumentiere das als Feature-Request..."

create_jira_issue:
  project_key: "FEAT"
  issue_type: "Story"
  summary: "Feature Request: Salesforce Integration"
  description: "## Customer Request
               Integration zu Salesforce CRM für bidirektionale Daten-Sync.
               
               ## Business Case
               - Customer: Beispiel AG (Enterprise-Kunde)
               - Current Pain: Manuelle Daten-Übertragung
               - Expected Benefit: 40h/Monat Zeitersparnis
               - Revenue Impact: Customer-Retention-kritisch
               
               ## Technical Requirements
               - Bidirectional Sync (Contacts, Deals, Activities)
               - Real-time oder Batch-Updates  
               - Field-Mapping-Konfiguration
               - Error-Handling und Conflict-Resolution
               
               ## Acceptance Criteria
               - [ ] Salesforce OAuth-Integration
               - [ ] Contact-Sync implementiert
               - [ ] Deal-Sync implementiert
               - [ ] Admin-UI für Field-Mapping"
  priority: "High"
  labels: ["feature-request", "integration", "customer-driven"]
  assignee_id: "product-manager-account-id"

Competitive-Intelligence:
  
Kunde: "Competitor XY hat Feature Z - haben Sie das auch?"

Issue-Creation:
  issue_type: "Epic"
  summary: "Competitive Analysis: Feature Z Implementation"
  labels: ["competitive", "feature-gap", "market-research"]
  
Linked-Issues:
  - Research Task: Competitive Analysis
  - Technical Task: Feasibility Study  
  - Business Task: ROI-Calculation
  - Product Task: Roadmap-Integration

Customer-Issue-Lookup:
  "customfield_10001 ~ '{customer_name}' ORDER BY created DESC"
  
Open-Issues-für-Customer:
  "customfield_10001 ~ '{customer_name}' AND status != Done"
  
Recent-Customer-Issues:
  "customfield_10001 ~ '{customer_name}' AND created >= -30d"
  
Critical-Customer-Issues:
  "customfield_10001 ~ '{customer_name}' AND priority = Highest"

Team-Workload-Queries:
  
Überfällige-Issues:
  "assignee = currentUser() AND due <= now() AND status != Done"
  
Heute-zu-erledigen:
  "assignee = currentUser() AND due <= endOfDay() AND status != Done"
  
High-Priority-Backlog:
  "project = DEV AND priority >= High AND status = 'To Do'"
  
Review-Required:
  "status = 'Code Review' AND assignee = currentUser()"

Performance-Tracking-Queries:
  
Bug-Rate-Last-Week:
  "issuetype = Bug AND created >= -7d"
  
Feature-Completion-Rate:
  "issuetype = Story AND resolved >= -30d"
  
Customer-Satisfaction-Issues:
  "labels = customer-escalation AND created >= -7d"
  
SLA-Violations:
  "priority = Highest AND created <= -4h AND status != Done"

Ursache: API-Token ungültig oder Basic-Auth falsch

Jira-Response:
  "errorMessages": ["You do not have the permission to see the specified issue."]

Fallback:
  "Jira-Zugriff nicht möglich. Ich dokumentiere das Problem 
   für manuelle Bearbeitung durch das Tech-Team."

Resolution:
  - API-Token neu generieren
  - Basic-Auth-String validieren
  - User-Permissions überprüfen

Ursache: Project-Key existiert nicht oder kein Zugriff

Graceful-Handling:
  "Das spezifische Projekt ist nicht verfügbar. 
   Ich erstelle das Issue im Standard-Support-Projekt."

Fallback-Logic:
  - Default-Project verwenden
  - Issue-Type auf "Task" ändern
  - Admin-Benachrichtigung über Konfigurationsfehler

Ursache: JQL-Syntax-Fehler oder ungültige Field-Names

Common-JQL-Errors:
  - Typos in Field-Names
  - Ungültige Operatoren
  - Falsche String-Escaping
  - Non-existent Values

Error-Recovery:
  - Fallback auf einfachere JQL-Query
  - Text-based Search als Alternative
  - User-friendly Error-Message

Custom-Field-Configuration:
  
Customer-Information:
  customfield_10001: "Customer Name" (Text)
  customfield_10002: "Customer Phone" (Text)
  customfield_10003: "Customer Email" (Text)
  customfield_10004: "Customer Tier" (Select: Basic/Pro/Enterprise)
  
Business-Context:
  customfield_10005: "Revenue Impact" (Select: Low/Medium/High)
  customfield_10006: "Urgency Level" (Select: 1-5)
  customfield_10007: "Call Source" (Text: "Mid-Call-Tool")
  customfield_10008: "Resolution Deadline" (Date/Time)

Jira-Workflow-Rules:
  
Customer-Issue-Workflow:
  Wenn Customer-Tier = "Enterprise":
    → Status automatisch auf "High Priority"
    → Assignee: Senior Support Engineer
    → SLA: 2 Stunden First Response
  
Mid-Call-Issue-Workflow:
  Wenn Labels contains "mid-call":
    → Priority mindestens "High"
    → Sofortige Assignee-Benachrichtigung
    → Customer-Update binnen 1 Stunde
  
Escalation-Rules:
  Wenn Priority = "Highest" UND 4h offen:
    → Auto-assign zu Manager
    → Customer-Benachrichtigung
    → Executive-Escalation