Forge app deep links

[eriklebel]

hi,
in trying to migrate my app from connect to forge, I cannot find a way to do a “deep link” to a page or space in my module.

I have two use-cases:

• links to an app resource
• re-directing the user to a specific view in the forge app (SPA) after an external handshake (using remotes).

https://{instance-url}/jira/apps/{app-id}/{module-id}#{view}

the closest I can get is “guessing” the app ID (based on the installation), and I cannot know the module ID.

This makes directing the users into the forge app impossible.

Is there a way to get a “friendly” module ID?

Does anyone else have this problem? Has anyone else solved this?

[SeanBourke]

Hey @eriklebel,

Based upon the URL you’ve shared, it looks like you’re planning on redirecting back into the jira:globalPage?

This URL will be represented in a standard format as https://{instance-url}/jira/apps/{appId}/{environmentId}/{anythingYouWant}. In this case, you’ll be able to persist your production environmentId in this url.

The Forge bridge createHistory method will make it easier for your app to read and interact with the anythingYouWant component of the URL.

[eriklebel]

Thank you Sean.

I did not know that the second ID was the environment ID. That is very helpful.

I will experiment with this and see how far I can take it.

Is any of this documented? if not, is it subject to change?

again, thank you.

[SeanBourke]

Hey @eriklebel,

The structuring of the url is defined in the jira:globalPage documentation which I’ve linked above.