Remove "Apps" label from JSM forge app

Forge Forge UI Kit and Custom UI
, ,
1

Hi,

I’m developing a Jira Service Management portal request detail panel using Custom UI and I have a question is it possible to remove the “Apps” label that looks like a header to whole portal request detail panel.

For example I have two elements in my jiraServiceManagement:portalRequestDetailPanel

jiraServiceManagement:portalRequestDetailPanel:
    - key: xjsm-reporter-customfilepicker-report-incident-portal-request-machines-panel
      resource: machinesPanel
      resolver:
        function: resolver
      title: Linked machines
    - key: xjsm-reporter-customfilepicker-report-incident-portal-request-incidents-panel
      resource: incidentsPanel
      resolver:
        function: resolver
      title: Incidents

image
image305×242 3.17 KB

It must be possible somehow, as when I tested some markeplace app that extends the portal functionality, it’s being shown without the “Apps” header.

image
image250×200 994 Bytes

Is it because my app is in the Development state?

2

Hey, I’ve got this issue too. My customer does not want any impact of installing a Forge app on other JSM projects.

I’m able to hide the app title by setting a non-standard whitespace character as the title of the module in the manifest. Along with rendering an empty element as the app, the impact is now significantly reduced. As there are no other Forge apps installed on this site though, there is still the impact of the “Apps” label now showing on the JSM Request Detail page.

I did some more investigating and it appears that:

  1. The Apps label is rendered after this private API request: /rest/servicedesk/1/customer/servicedesk-data/forge/fetch-extensions.
  2. This populates an extensions array which is checked within view/forge-ui/request-details-main-section/request-details-main-section.tsx.
  3. If there are any valid Forge apps, it renders <Headline>Apps</Headline>.

I would have expected that this label would be prevented by the page recognising contexts where the app isn’t allowed through Display Conditions, and if there are no apps for this context, don’t show the Apps label. I wouldn’t hold my breath for Display Conditions coming to JSM any time soon though, as it looks like Atlassian’s gone in a different direction:

On reviewing Atlassian’s code, I’ve learned that the way to mark Forge apps as only eligible for showing on certain JSM projects is through the Atlassian Guard Standard Data Security Policy feature. See the Developer’s guide on this. In this scenario, if an org admin sets your Forge app as ‘block by default’, then ‘allow’ on specific projects, then if there are no allowed Forge apps in context, Atlassian won’t show the Apps label.

Hope this helps!