Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Forge app can't call backend when a customer views a request in Jira Service Management

Illés Ákos
Contributor
January 23, 2025

I'm developing a Forge app to list all the remote links on the customer portal request UI. I think I managed to give the app the correct scope and unlicensed access permissions, correct me if I'm wrong here are relevant parts of the manifest (some scopes are likely redundant):

 

 

modules:

  jiraServiceManagement:portalRequestDetailPanel:

    - key: issuelink-details-hello-world-portal-request-detail-panel

      resource: main

      resolver:

        function: resolver

      render: native

      title: Linked Issues

      unlicensedAccess:

        - customer

        - unlicensed

permissions:

  scopes:

    - read:jira-work

    - read:issue.remote-link:jira

    - read:issue:jira

    - read:servicedesk-request
The problem is most likely with the permissions, because when I view the request with an agent user I can see the results and everything works fine, but when I view the request with a customer account I get this error in the browser's developer console (This is before the app runs):
POST https://MYCOMPANY.atlassian.net/rest/atlassian-connect/latest/addon-access 403 (Forbidden)
And this error when the app runs: 

GET https://api.atlassian.com/ex/jira/SOMENUMBERS/rest/api/3/issue/MYISSUEKEY/remotelink 403 (Forbidden)

The second error is because of the request I try to make to get the data from the REST API:

 

const res = await requestJira(`/rest/api/3/issue/${issueKey}/remotelink`);
I imported @Forge/bridge requestJira and I use UI Kit for displaying the data.
I'm new to forge app development, please help me resolve my issue.

1 answer

0 votes
Illés Ákos
Contributor
January 28, 2025

I managed to resolve the second issue. The problem was that I was missing a scope, namely: 

read:status:jira, also I realized, that the REST API documentation lists all of the scopes needed for a call, and also I switched to the forge/api requestJira method, because it can be called with app privileges. The first error is still a mystery.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
atlassian, atlassian community, journeys for jira service management, journeys for jsm, eap jsm atlassian, early access program atlassian, early access program journeys atlassian, early access program journeys jira service management, join atlassian eap

Join the Early Access Program (EAP) - Journeys for Jira Service Management 🚪

Journeys is a brand new feature in Jira Service Management that helps you streamline various processes in your organization that may cross multiple departments, such as employee onboarding or off-boarding that require action from different teams. ✨

Join the EAP →
AUG Leaders

Atlassian Community Events