Environments in plugin development stage


What should the plugin environment look like in a team with several developers? In a ‘typical’ project scenario, each developer would have a local environment (equivalent to a private Jira Cloud instance), and then there would be several public environments like dev, stage, and prod that are not for day-to-day work.

I find that having only one environment in which programmers would work every day would cause a lot of conflict.
But what do you think?

Have you tried adding your developers as collaborators and using custom environments so you can each have a unique dev environment?


It looks like this is what I’m looking for!
Could you assure me that every environment has separate storage?
And one more thing, is there a possibility to restraint access to applications in non-production environment for users?

Hey hi Nowak,

Storage quota and usage is installation based https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/#total-storage-capacity-quota. You can get more details on storage information of your app in developer console https://developer.atlassian.com/platform/forge/view-app-storage/

We have treated production environment for forge apps as a special case and handled roles and permissions for contributors accordingly. As of today, any team member added to your app can view the dev and staging specific logs, storage key value pairs etc. We have not gone deep into environment specific permissions.