Q1: A Jira instance is not being created when triggered from Rocketlane. Why might this happen?
A: The most common cause is a permissions issue on the Jira side. The Jira error message in such cases typically reads: "The target project doesn't exist or you don't have permission to create issues in it." This means the Jira user account connected to the integration does not have the required access to create issues in the target Jira project. Check that the connected Jira user has the necessary permissions for the specific issue type and project in Jira.
Q2: The Jira user connected to the integration appears to have permissions. What else should I check?
A: Even if the connected user appears to have general access, verify that they specifically have permission to create the relevant issue type in the exact Jira project being targeted. Permissions may be granted at a broad level but restricted for specific issue types or projects. Confirm this directly in Jira's permission settings.
Q3: Could the project manager's Jira access affect whether the Jira instance gets created?
A: Yes. If the integration requires the project manager's Jira access as part of the creation process, then the project manager must also have the required Jira permissions. Insufficient access for any user involved can cause the creation to fail. Verifying and correcting the project manager's Jira access level resolved this issue in practice.
Q4: The error seems to be coming from Jira, not Rocketlane. What should I do?
A: If the error message originates from Jira (e.g. "The target project doesn't exist or you don't have permission to create issues in it"), the root cause lies within Jira's permissions or project configuration, not Rocketlane's setup. In this case, contact Jira's support team for further investigation. If Jira's support identifies anything on the Rocketlane side as a contributing factor, loop in Rocketlane support at that point.
Q5: How can I confirm whether the failure is permissions-related or something else?
A: Check the error/debug logs in the integration job. A permissions-related failure will show a clear error from Jira such as "The target project doesn't exist or you don't have permission to create issues in it." If the error message differs, the cause may be something else — such as a misconfigured field, a missing required value, or a connectivity issue — and further investigation would be needed.