One of the biggest things that helps with scaling Jira is having a test environment. For small instances, it could be that the test environment is just a test project. For larger environments, it’s important to have a test instance and, in some cases, two test instances. Several things can be changed on the fly within Jira; however, as the company grows, it’s essential to turn these processes into a more scalable solution.
Here’s an example of why a test environment is important. If there’s a workflow that’s attached to 15 projects and a change needs to be made, changes shouldn’t be made to the existing workflow. It’s best if the changes are made within a test environment, verified, and then made live. If something goes wrong, it’s a lot easier to verify it when it’s in a test environment, instead of blocking 15 project teams from working.
Another example involves permission changes. If you plan on making changes to a permission scheme, you could end up blocking people from accessing a project. It’s better to test the permission scheme changes before making them live.
The following are ways to create testing environments:
- Test project within the live environment
- A second instance
- A stage environment and a dev environment
Consider using these options when making significant impact changes to projects or your environment. It’s an important practice that will keep your environment healthy.
Sign up to receive more great content
Learn more about Atlassian and how Isos can help by signing up to receive our latest blogs, eBooks, whitepapers and more.
Training Made Easy: Four Great Atlassian University Classes for Beginning Jira and JSM Users