Forge deploy sandbox enviroment

[José Torres]

Hello, community!

I'm deploying Forge applications in Jira Cloud, but I have a question: how can I use a Sandbox environment to replicate deployments using the same code without having to duplicate the solution with new IDs? How have you handled this process?

[Thomas Blevins]

Hey, I do not work for Atlassian, so I could be wrong here.  I although, think I am going through the same scenario, and below is my understanding on the best way to set up an environmental workflow.

I think the Environments documentation describes what to do here, in the first three paragraphs.  So, I will have three total sites, accomplished with the Cloud Developer Bundle:

• The production site (company.atlassian.net), where my team collaborates with VERY REAL data
• The staging site (staging-company.atlassian.net), where I proof my changes to my team/management before sending them to "production"
• The development site (development-company.atlassian.net), where I actively develop changes on, with the usage of `forge tunnel`.

From there, each site installs an environment of my deployed application.

[Tomislav Tobijas]

Might not be 100% relevant here, but I know scenarios where folks are strugling when it comes to field IDs (which kind of relates to Forge as well) and that there's this suggestion that would support sync between prod and sandbox when it comes to such entities: CLOUD-12399: Enhance the consistency of custom field IDs between production and sandbox environments in Jira Cloud