JSM Portal + Forge: How to reliably get customer accountId/email while filling request form?

[Peter Reiser]

I’m building a Forge app with a jira:customField rendered in JSM portal-request using Custom UI.

I call view.getContext() in the field UI, but for portal customers I get accountId: null. I do get portal/request context like portal.id and request.typeId, but not a usable user identity.

Question:

Is accountId expected to be unavailable for portal customers in jira:customField on portal-request?
If yes, is there any supported way to identify the current portal user during request creation?
Or is post-create handling via the created issue’s reporter accountId the only reliable approach?
I checked the Forge docs for view.getContext() and unlicensed access, but couldn’t find a clear answer for this specific module/context.

Best regards

Peter

[Marc -Devoteam- · Accepted solution]

Hi @Peter Reiser 

Might be better to raise oyur issue via https://community.developer.atlassian.com 

But if a customer is not on a space or listed in Atlassian, this customer has no account ID yet.

Otherwise this is the API endpint https://<instancename>.atlassian.net/rest/api/3/user/search?query=<emailAddress> 

And I think in forge you can only use the API endpoint as well.

[Peter Reiser]

@Marc -Devoteam-  thanks I will raise the question in the dev community