Jira Cloud integration with Firebase gets on a spinning wheel after entering API credentials and saving
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Jira Cloud integration with Firebase gets on a spinning wheel after entering the credentials and clicking "Verify & save", using developer tools, the error message below can be found under the network requests:
code: 400, message: "Request contains an invalid argument.", status: "INVALID_ARGUMENT"
For the endpoint:
- Jira Cloud
The Jira Cloud integration within Firebase makes two requests when integrating:
- This API returns information about the Jira instance:
- This API returns details of projects, issue types within projects, and, when requested, the create screen fields for each issue type for the user. Use the information to populate the requests in Create issue and Create issues:
The last call gets all information on what's needed to raise an issue as a bug, it would return an HTTP 200 status even if the issue type does not exist, because it returns an empty search for the project. This is not the cause as the error thrown by Firebase is NOT_FOUND for the missing issue type scenario.
The error for INVALID_ARGUMENT can be reproduced on the Firebase console by making a field required for the Bug issue type.
There is a required field on the project's field configuration scheme for the Bug issue type.
Make the field optional or remove it from the screen used by the Bug issue type create screen.