I’m deciding whether it is correct to enable pinning for our Forge App. Our app has a bit of an edge case in that we are importing data into another marketplace app, but that app has data residency enabled. The app only stores settings and some metadata about issues, so maybe pinning isn’t important.
Correct me if I’m wrong but my understanding is that pinning means a customer can request for in-scope data to be relocated to the same location as their Jira instance. So in this case that depends if the settings and metadata your app exports to another app are in-scope data and if they are, while you did not share the underlying implementation of the data export mechanism but if it’s an egress of in-scope data, then the app shouldn’t be eligible for a pinned status based on the documentation on Forge runtime egress permission.
All that wouldn’t be relevant if you’re not dealing with in-scope data but if you are, unless Atlassian allows some sort of declaration that the egress of in-scope data is to another Marketplace app that supports data residency that must be installed together with your app (it sounds convoluted even as I type it out 
), I’m not sure how to achieve a pinned status in this scenario.
1 Like