Skip to main content

Troubleshoot Ticketing Integrations & Ticket Creation Failures

NudgeBee integrates with Jira, ServiceNow, GitHub Issues, GitLab, and PagerDuty to automate incident creation and ticket tracking. This guide diagnoses common ticket creation failures, custom field mapping errors, and sync issues.

1. Diagnostic Decision Tree for Ticket Failures​

2. Common Ticket Creation Failures & Solutions​

Failure 1: Mandatory Jira Custom Fields Missing​

  • Symptom: Ticket creation fails with Jira API Error 400: Field '<field_name>' is required.
  • Cause: Your Jira project has required fields (e.g. Component/s, Root Cause Category, Environment, Team) that were not filled in NudgeBee's default ticket template.
  • Remediation:
    1. In NudgeBee Console, go to Settings $\rightarrow$ Integrations $\rightarrow$ Tickets $\rightarrow$ Jira.
    2. Inspect the ticket creation form or workflow ticket task for the selected project and issue type.
    3. Supply the required fields using the available field metadata. If a needed field is unavailable, collect the project, issue type, field ID, and error for support.
    4. Save changes and retry ticket creation.

Failure 2: ServiceNow Incident Creation Fails (Table Not Found or 403 Forbidden)​

  • Symptom: ServiceNow returns 403 Forbidden: User not authorized to insert into table incident.
  • Cause: The ServiceNow integration service account lacks the itil or incident_manager role, or Access Control Lists (ACLs) restrict API writes to the incident table.
  • Remediation: In ServiceNow Admin Console, assign the itil role and ensure REST API write access is enabled on the target table.

Failure 3: Reporter or Assignee is Not Assignable​

  • Symptom: Jira API Error: User '<email>' cannot be assigned issues in project '<PROJ>'.
  • Cause: In Jira Project Settings $\rightarrow$ Permissions, the user account associated with the NudgeBee API token lacks the Assignable User permission.
  • Remediation: Grant the integration user Assignable User and Create Issues permissions in the target project's permission scheme.

Failure 4: Jira Ticket Status Is Stale​

The Jira sync fetches issue details and updates NudgeBee ticket records. Check the linked issue ID, configured credentials, access to that issue, and ticket-server sync errors. See Jira troubleshooting.

Ticket status and event triage status are separate. This flow does not require a Jira status-sync webhook and does not guarantee that closing a ticket resolves a linked event.

Ask NuBi in chat for guided ticketing integration assistance:

  • "How do I fix Jira API Error 400 when mandatory custom fields are missing?"
  • "What ServiceNow permissions are required for incident creation?"