404 not found errors on jira api's using forge/api

Forge Forge UI Kit and Custom UI
, ,
1

I’m encountering persistent 404 errors when making Jira API calls via requestJira in my Forge app. It is a react app with node runtime version nodejs18.x.

The issue actually started back in March 2024 and there were zero code changes to this app, indicating that something in forge changed that my app is now not happy about. I have read through change logs etc and can’t find any smoking guns.

The issue specifically seems to be invalid endpoints (E.g. https://nebulas-dev.atlassian.net/rest/api/latest/user/properties/jsm-cmdb-upsell-page-dismissed?accountId=XXXXXXXXXXXXXXXXX). I have checked the user properties endpoint and most of the properties in the endpoint do NOT exist.

I have tried updating packages etc but cannot seem to find exactly how to resolve this issue. Everything was working fine with the app for about a 9 months and then one day just started failing. So any interaction with Jira is broken, however interactions with external API’s is working fine.

Please let me know what additional information will help?

Thanks in advance.

2

Hello @RobertHarkin

To me, jsm-cmdb-upsell-page-dismissed sounds like a user property that Atlassian or someone else created to track whether or not a user has dismissed a page where they were encouraged to try Jira Service Management’s Asset and Configuration Management service. It might have been part of an ‘upsell’ marketing campaign and, now that the campaign is over, the property has no further purpose and creator has deleted it, hence the reason it no longer exists.

In your Forge app, what are you using that property for? Why are trying to get or set its value?

3

Hi @sunnyape

Thanks for your response and sorry for the delay. I had a couple of tech free days for a birthday.

Very good question which helped me see forest for the trees. The short answer is that I am not doing this. Had to remember Atlassian apps are apps (Mine) on app (Atlassians).

Obviously Atlassian is making these calls and the failures have nothing to do with my error within my app/plugin.

My api calls are now failing I think due to the following:

Disallowing path manipulation attempt

Thanks for putting me on the right path. I think I know how to fix this issue now by constructing the URL’s in once place.

As it’s still related to this topic I may post back here if I get stuck.

Thanks again.