jiraServiceManagement:portalRequestViewAction is broken

Hey,

has anyone ever got a jiraServiceManagement:portalRequestViewAction module running on Custom UI? I assume this module is broken. Deployments of an according manifest.yml are rejected by Forge servers.

minimal manifest.yml to reproduce (app id removed):

modules:
  jiraServiceManagement:portalRequestViewAction:
    - key: actions-view
      resource: actions-res
      title: Actions
      icon: https://user-images.githubusercontent.com/11311357/165253968-fd219c65-0150-411c-840a-554b2942e4a2.svg
  function:
    - key: resolver
      handler: index.handler
resources:
  - key: actions-res
    path: static/actions/build
    tunnel:
      port: 3002
permissions:
  scopes:
    - storage:app
    - read:jira-work
    - write:jira-work
app:
  id: ari:cloud:ecosystem::app/xx

verbose error logs:

ℹ Validating manifest
  Upload URL is valid
  Found manifest file
  Manifest is a valid YAML
  Manifest validation failed
Validation errors: {
  "validationResult": {
    "tid": "ea30ceae3b094581",
    "code": 400,
    "type": "UpsertEnvironmentRequestInvalidError",
    "message": "Upsert Environment Request body is invalid. Details "
  }
}

Error: Deployment failed

Error: Deployment failed
    at ArtifactDeployer.handleErrorEvent (/Users/jwolf/.local/share/nvm/v16.15.0/lib/node_modules/@forge/cli/out/deploy/deployer/deployer.js:151:15)
    at ArtifactDeployer.pollAndCheckEvents (/Users/jwolf/.local/share/nvm/v16.15.0/lib/node_modules/@forge/cli/out/deploy/deployer/deployer.js:61:18)

I assume the only alternative is switching to Connect here. Has any Atlassian some insights about this?

Cheers
Julian

2 Likes

Hi Julian,

There was indeed a problem with this module and that has been addressed after your report (thank you for flagging it with us).

Can you try again and let us know if it’s working now?

Thanks,
Caterina

Hi @ccurti

I can confirm that the module is now working as intended. The modal is opening, the Custom UI gets rendered. I’ll keep you updated in case we will stumble across other blockers. Thank you for the quick assistance on that. Really appreciate it!

Cheers
Julian

Hey @ccurti

After digging deeper we unfortunately ran into another roadblock here. The modal of portalRequestViewAction is missing any context information. There is no way to find out the issueKey of the according ticket where the modal was opened from. So there is no possibility to show any request related information or actions which makes the module barely useful.

Extension context of portalRequestViewAction :x:
image

Extension context of portalRequestDetailsPanel :white_check_mark:
image

Would you please report this to the development team?

Cheers
Julian

1 Like

Hi @JulianWolf ,

I brought the lack of context with the engineering team and the [FRGE-796] - Ecosystem Jira request has been raised now.

Are you able to provide which context do you think would be required on the FRGE ticket directly? E.g. would what is available on the https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-service-management-portal-request-detail-panel/#extension-context be enough or do you see any other information that would be required?
If any are not relevant, we would like to know as well.

Thanks,
Caterina

1 Like

Hi @ccurti

thank you for raising that ticket. We would expect the same context information as in the other modules (like portalRequestDetailsPanel). portalId, requestKey and typeId are required to offer more functionality which correlates to the request where the portRequestViewAction was opened from.

Do you have any time estimation on when this will be fixed? Any information would be appreciated as we’ve to decide whether to start a new project on Forge or Connect.

Cheers
Julian

2 Likes

@JulianWolf the team is reviewing what is needed to add the additional context.

No promises but, if everything goes well, it should be available in less than a month. Any updates will be posted on the ticket and you can ask there for an update as well.

Caterina

2 Likes