nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA admin test environment

Darya_Koyfman

I'm JIRA administrator, not a programmer. We use JIRA for engineering processing, and I lead these processes. As an admin, I have to sometimes change/upgrade processes and this includes change of workflows, schemes, screens, etc. I know I have to work with the copy first, and then tag the project to the new version of whatever was changed. But now, I have a tremendous change of a workflow, and I'm afraid to screw up the production by loosing data or somehow else.

Our IT created the snapshot backup of the existing JIRA. Should this be ebough for rollback in case of a problem, or we need to create test environment and what's the best way to do it?

Accepted answers

somethingblue

Hi Darya,

I always recommend making changes and testing in a test environment before making those changes in a production environment so you can judge the impact on the instance.

In the event something goes wrong with your workflows the XML backup should be enough to restore JIRA, however, you may also want to export the workflow you're going to modify as an additional backup.

You can restore a copy of your instance to another clean installed instance and license it with a dev license to test. I have included some additional resources that should help you get started:

Working with workflows

Managing your workflows

Backing Up Data

Rolling back a JIRA application upgrade

Cheers,

Branden

Vijay Sv

Always use TEST or DEV instances of Jira instead making changes on the Live production system.

Once you validate all the changes in TEST, use workflow import/export (local system) to move new workflow in Prod.

Importants:

>> Refresh your TEST or DEV DB instances with Production Copy and re-index the instance. So that you get latest data to workon.

>> Old Status and new status mappings need during migration(from TEST to Prod).

Good Luck!

All comments

somethingblue

Hi Darya,

I always recommend making changes and testing in a test environment before making those changes in a production environment so you can judge the impact on the instance.

You can restore a copy of your instance to another clean installed instance and license it with a dev license to test. I have included some additional resources that should help you get started:

Working with workflows

Managing your workflows

Backing Up Data

Rolling back a JIRA application upgrade

Cheers,

Branden

Darya_Koyfman

Thank you Brandon!

Vijay Sv

Always use TEST or DEV instances of Jira instead making changes on the Live production system.

Once you validate all the changes in TEST, use workflow import/export (local system) to move new workflow in Prod.

Importants:

>> Refresh your TEST or DEV DB instances with Production Copy and re-index the instance. So that you get latest data to workon.

>> Old Status and new status mappings need during migration(from TEST to Prod).

Good Luck!

vivuu

Can you please explain how we can create a Test environment of Jira from the PROd.

Jira version 7,1.9, Windows server

DB - MSSQL 2012

Vijay Sv

Here you go..

1. Take a Database backup of production DB

2. Install the Jira version in window server and configure with the TEST db server.

3. Set-up the required test base URL.

4. Disable notifications.

5. Once you set-up new Jira TEST instance and connected to required DB (should be pointing to Jira TEST DB), restore the production DB copy in TEST database.

6. Stop Jira Services and remove the cache from the application home directory and restart the services.

7. Run "Lock and re-index" and once it's complete revisit the base url and change it to TEST jira url.

Note: Make sure you have disabled the notifications from TEST instance.

Thanks,

Vijay

vivuu

Thanks Vijay. Will follow the steps

vivuu

As the Prod Db is already restored by the DB team in TESt environment , We have installed the new Jira instane in test environment and we cant map the restored DB with the new Jira Test instance.

Getting elow error while mapping it with the restored DB

"You have specified a database that is not empty, please specify an empty database. If you want to upgrade an existing installation, please follow these instructions instead."

vivuu

Now Our Prod setup- JIRA -7.1.9 in Windows server and it should be migrated to linux machine in another domain with a different url .

currently in windows the atlassin application are running behind reverse proxy and for authentication we are using crowd internal directory ?

So please let us know what are the steps need to be implemented for data migration to new instance in the linux (windows to linux )

using MSSQl DB in both environment

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-administration

jira-core