Forge app: JSM portal header not shown to Customers

Hi All,

I’m trying to display information about their Organization for the Customers. The panel will display the Agents, but not for Customers.

Here is my manifest.yml:

modules:
  jiraServiceManagement:portalHeader:
    - key: customer-knows-remaining-forge-hello-world-panel
      function: main
      title: Customer knows Remaining
  function:
    - key: main
      handler: index.run
app:
  id: ari:cloud:ecosystem::app/a1bf0201-2b5a-48de-a89d-3effe6b456ba
  runtime:
    snapshots: false

and here is my index.jsx:

import ForgeUI, { render, PortalHeader, Heading } from '@forge/ui';

const App = () => {
    return (
            <Heading>Verbleibende Stunden auf Ihrem SLA</Heading>
    );
};

export const run = render(
    <PortalHeader>
        <App />
    </PortalHeader>
);

In the logs of forge tunnel I don’t see that the app is triggered:

forge tunnel
Tunnel redirects requests you make to your local machine. This occurs for any Atlassian site where your app is installed in the development environment. You will not see requests from other users.
Press Ctrl+C to cancel.

Checking Docker image... 100%   
Your Docker image is up to date.

Reloading code...

=== Running forge lint...
No issues found.

=== Bundling code...
App code bundled.
App code reloaded.

Listening for requests...


Stopping tunnel...
Tunnel stopped.

while when I open the portal as an agent, I see a trigger message:

forge tunnel
Tunnel redirects requests you make to your local machine. This occurs for any Atlassian site where your app is installed in the development environment. You will not see requests from other users.
Press Ctrl+C to cancel.

Checking Docker image... 100%   
Your Docker image is up to date.

Reloading code...

=== Running forge lint...
No issues found.

=== Bundling code...
App code bundled.
App code reloaded.

Listening for requests...


**invocation: 6a1f2e49686eeb2d index.run**

Stopping tunnel...
Tunnel stopped.

Did I miss somthing here?

Thanks in advance. Kind regards,

Roman Maire

3 Likes

We have a feature for this [FRGE-189] - Ecosystem Jira. This address the use case mentioned here.