Hello,
I am trying to test my forge app internally while the app is in development or staging environment. I want other users inside my company to be able to access the app. However from the Attlassian documentation, the only suggessted way is to deploy to production and distribute the app via an installation link. I do not want to put the app to production without having it tested thoroughly, so is there a way that other internally users that have jira account can test my jira-cloud app even though it is in development or staging environment. Also a following up question, if the answer to the above question is no, then what would be the difference and usage of having two different environments: development and staging.
Thank you in advance.
Hello,
I’d say this depends mostly on which site you want to test your app on. If you’re testing on your own dev site you can invite users but be careful as you are limited in terms of number of free licenses (5 for Jira/Confluence or 1 for JSM so do not grant them access to it).
Otherwise they could create their own dev site and install the app there via Forge CLI (you can add them as contributors to your app in the dev console)
Ultimately maybe a sandbox site could be more suited to this kind of shared testing environment
Mathieu
Hello @QToolavlcom , you can use the staging environment for testing. First, deploy to staging using the command forge deploy -e staging. Then install your Forge app on your company Jira instance using forge install -e staging.
If you want to integrate the license, use forge install -l active -e staging so the license is activated by default. After that, add the user as a contributor in the developer console: https://developer.atlassian.com/console/ . Now users in that instance can use the app similar to production, without deploying to production.
