Automating staging environments for Jira Part 1
We recommend customer set up Atlassian Jira staging environments. Unfortunately, many customers decide they don’t want to build and maintain a second system. If a staging system is there, it’s rarely kept up to date. This occurs because refreshing a staging environment is a tiresome and error prone task.
Mistakes in the process can have dire consequences. The staging server could:
- Process the inbound emails of the production one.
- Send incorrect notifications to users
- Mislead an admin into thinking they’re making changes in one system instead of the other
- Redirect admins to the wrong system without them noticing (due to bad base URL)
To help mitigate this, we have created a baseline SQL script which you can tweak to match your needs. This will allow you to quickly, easily, and consistently update your Jira staging environment. Now you can go to the beach and relax while your automated staging environment gets updated regularly.
Code is below and on Bitbucket. Part 2 of this will handle the changes that we recommend at the filesystem level.
We promise we don't send spam