Forge app in customer portal shows for customers with JSM tech access but not JSM customer access

Forge Forge UI Kit and Custom UI
1

I have a forge portal app that is in the portal footer. It displays for everyone that has a JSM license or Jira software license, but the users that just have the JSM Customer license can’t see the button. No errors or anything, the forge app just doesn’t even fire up when they enter the portal. I’ve opened a support ticket on this also, but wondered if anyone here has seen this issue. The JSM Customers all have Atlassian id’s, so they’re not anonymous.

2

@EricKruegerStrataCom,

I’m not deep on JSM but I’m aware that different types of users may have different access models by module. Maybe you’ve seen this already?

https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-jsm-users/

3

I actually found this a few minutes after I posted. I think this will fix my issue. It’s a little counter-intuitive that you have to mark an app special for use in the portal for what are essentially portal users. I believe the sample apps should have that flag set automatically. The customer I’m working with has almost half their company using either Jira software or JSM as a tech, so testing this has been a challenge…actually finding someone to test who isn’t a licensed user. Thanks!

4

Thanks Eric, that’s good feedback. Perhaps we’ll change the app templates.

2 Likes
5

Hello, I need help with this exact issue. My app is published, but my clients are not able to see the app on the issue creation screen. However, if you log into the portal with a user who has Jira agent access, it shows up.

my manifest

modules:
  jiraServiceManagement:portalRequestCreatePropertyPanel:
    - key: -ticket-search-field-hello-world-portal-request-create-property-panel
      resource: main
      resolver:
        function: resolver
      viewportSize: large
  function:
    - key: resolver
      handler: index.handler
resources:
  - key: main
    path: static/hello-world/build
permissions:
  content:
    styles:
      - unsafe-inline
  scopes:
    - read:jira-work
    - read:servicedesk-request