Skip to main content

Common Jira Integration Errors

  • Updated

You do not have permission to create WebHook 'mNoibu webhook

Cause:

This error occurs when the Jira account being used for the integration does not have sufficient permissions to create webhooks. Webhooks are required for syncing updates between Jira and Noibu.

Solution:

The account used for the Noibu integration must have permissions capable of creating webhooks in Jira, which generally requires a super user (Jira Administrator).

Steps to Resolve:

  1. Ensure the Jira Account Has Webhook Creation Permissions:
    • The user account must have the Administer Jira global permission.

    • Typically, only Jira Administrators or super users have this level of access.

    • To check:

      • Navigate to Jira Administration > System > Global Permissions.

      • Confirm that the user has the Administer Jira permission.

  2. Verify API Token & Authentication Credentials:
    • Noibu requires a Jira user email and a personal API token for authentication.

    • Ensure that:

      • The API token is generated from Atlassian’s API Token Management page.

      • The user email and API token combination is correct in Noibu’s integration settings.

      • The API token is active and not expired.

  3. Confirm API Permissions for the User Account:
    • In addition to webhook creation, the user must have:

      • Browse Projects – Required to list available Jira projects.

      • Create Issues – If syncing issue creation.

      • Manage Webhooks – Ensures the webhook can be created and managed properly.

  4. Try a Jira Super User or Admin Account:
    • If the current credentials lack the necessary permissions, use an account with Jira Administrator privileges.

    • This ensures all required permissions are granted during setup.

 

Client must be authenticated to access this resource

Cause:

This error occurs when Noibu is unable to authenticate with Jira using the provided credentials. Common reasons include:

  • Incorrect email or API token used for authentication.

  • Expired or revoked API token.

  • Jira account lacks necessary API permissions.

  • Firewall or network restrictions blocking Noibu’s request.

Solution:

  1. Verify API Token & Credentials:
    • Ensure that the correct Jira email and API token are entered in Noibu.

    • The API token must be generated from Atlassian’s API Token Management page.

    • Double-check that the email and token match the Jira account used for integration.

  2. Check API Token Status:
    • If the API token was recently revoked or expired, generate a new API token and update it in Noibu’s integration settings.

    • Avoid using older, inactive tokens.

  3. Confirm API Permissions for the Jira Account:
     The Jira account used for authentication must have:

    • Browse Projects – To retrieve Jira project details.

    • Create Issues – If issue creation is enabled in Noibu.

    • Manage Webhooks – Required for syncing issue updates.

    • Administer Jira (Super User) – If webhook creation is required.

  4. Ensure Proper Authentication Format:
    • Noibu requires Basic Authentication with an API token, formatted as follows:

      • Email: your-email@domain.com

      • API Token: (Generated from Atlassian)

  5. Check Firewall or Network Restrictions:
    • If your company enforces IP restrictions, verify that Noibu’s servers are whitelisted to communicate with Jira.

    • Contact your IT team to ensure Noibu’s requests are not blocked.

  6. Test Authentication with a Jira API Request (Optional):

Use the following command to verify authentication via API:

curl -u your-email@domain.com:your-api-token -X GET "https://your-domain.atlassian.net/rest/api/3/project"

  • A successful response confirms that authentication is working correctly.

Articles in this section