Integration troubleshooting

Taiga project not found#

1. Confirm the base URL ends at the API root expected by the deployment.
2. Confirm the project slug or numeric ID.
3. Confirm the token can read that project.
4. Run Test Connection again.

The connection test distinguishes a numeric project ID from a slug.

Jira project not found#

1. Confirm the Jira site URL.
2. Confirm the project key, including capitalization.
3. Confirm the token is valid for the site and project.
4. Run Test Connection again.

Notifications are missing#

The engine supports Mattermost, Slack, Teams, and SMTP email. Check only the channel you enabled:

• Provider URL or SMTP host and port.
• Secret availability in the runtime secret store.
• Recipient or channel configuration.
• Notification cooldowns.
• The run log for a provider response.

Never paste a webhook URL, SMTP password, or bot token into a ticket.

n8n replanner approval flow fails#

The checked-in n8n JSON is an import template. It has not been validated against the current n8n instance and uses environment-variable expressions for secrets, which current n8n guidance recommends replacing with credentials.

Before production use:

1. Import into a non-production n8n project.
2. Replace secrets with n8n credentials.
3. Add explicit webhook authentication and failure handling.
4. Validate node versions and every connection.
5. Test with pinned data and a non-production Taiga project.
6. Publish only after the connection graph and outputs are verified.

Pull-request linking is empty#

Cycle P is optional. Confirm SCRUM_PR_LINK_ENABLED, the provider selection, repository information, and a GitHub or GitLab token. Missing or inaccessible pull requests should not block unrelated cycles.