Background
When running the configuration validation checks on a ticketing integration configuration in RealTheory, the Validate Project Key check fails with the following message:
Check unsuccessful \- Project does not exist
This failure will prevent the integration from functioning correctly and usually signals an issue with the credentials, project permissions, or ticketing system environment rather than a formatting problem with the Project Key itself.
Problem
While inline validation might appear successful, it does not verify whether the specified user has access to the project. The Validate Project Key check verifies that, and a check failure indicates that the named user cannot authenticate to the project or lacks the necessary permissions.
Solution
Check for the following, and then retry the validation:
Credential Issues
- An incorrect username or API token (secret).
Confirm that the username/API token is correct and active. - The user does not have permission to create issues in the specified project.
Ensure the user has permissions to browse and create issues in the project.
Ticketing System Project Issues
- Role-based access control (RBAC) or project-specific permissions prevent the user from accessing the project.
Ensure the user has permissions to browse and create issues in the project.
Ticketing System Environment or Connectivity Issues
- The ticketing system is temporarily unavailable or returning errors (maintenance, rate limiting, or misconfigured proxy).
Verify that the ticketing system is accessible through other means.