Hi @PABLO ANDRES BUILES RAMIREZ
The 403 Forbidden error indicates that the request to the Jira API is being blocked, which is mostly due to authentication or permission issues. Sp try to First, check your authentication details to ensure they are correct. If you're using an API token, make sure it is valid and included in the request headers. For Jira, the Authorization header should follow the format: Authorization: Basic <base64-encoded-email:api_token>. If you're using Basic Auth, double-check that the email and token are accurate.
Next, verify that the user or API token you're using has the necessary permissions to access the resource. If permissions are restricted, you'll need to update them in Jira’s user or project settings. Additionally, if your organization has IP whitelisting enabled, ensure that the IP address you're making the request from is added to the whitelist in Jira’s security settings.
If the problem persists, the resource you’re trying to access might not exist, or the endpoint URL could be incorrect, so double-check these as well.
Dd
Hello, we already checked and now the problem is not due to authentication or permissions blocking, but rather that it does not load the form fields, it tries to load them but it remains blank. The response that returns is a code 200
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Code 200 means the request was successful, but the response body may be incomplete or malformed.(client-side rendering or configuration issues).
inspect the API response to ensure it contains the correct field data. If the response is valid, check the browser console for JavaScript errors that might indicate problems with rendering or data parsing. Ensure the fields are correctly configured in the Create Issue Screen for the project and issue type, and confirm their context matches the project. Clear browser and Jira application caches to rule out caching issues. If plugins or custom scripts are in use, disable them temporarily to identify conflicts. Finally, enable Jira debug logs to pinpoint any backend errors related to field loading.
Dd
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like there’s an issue with the customer portal’s access. This could be caused by several things, such as:
1. **Permissions Issue**: Ensure the user has the proper permissions to view the portal. Check the Jira settings for any restrictions on customer access.
2. **Portal Configuration**: Verify that the portal is correctly configured in Jira, and that the right project and request types are available to customers.
3. **Login Issue**: Double-check if the customer is logged in with the right credentials, or if there’s an authentication error causing the access problem.
You can troubleshoot these steps just like you would hunt for great *Torrance Food Specials*—start by checking the basics, and the solution may be right under your nose!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.