Best practice for testing JIRA customizations ?

[Karthik Bhat]

Hi,

If I am doing some customizations in JIRA, like testing a new plugin or adding a new scheme, as an administrator and I dont want to make the system live to my end users before I test it thoroughly, what is the best practice that I should follow?

I cannot take the system down every time I try something new in JIRA. Please comment. Thanks in advance.

[Thomas Schlegel · Accepted solution]

Hi Karthik,

you need a Jira test system that has the same configuration as your real system. That's the usual way of testing new plugins or other system changes.

Cheers

Thomas

[Karthik Bhat]

How do I bring up a test system with the same configuration as my real system? Can you please elaborate more or provide me the link if this is documented already? I dont need the attachments from the real system since it might take a lot of time to replicate. Thanks!

[Bob Swift]

I would recommend you follow the same procedures you would use if you lost your primary system and needed to recover. Restore DB and home directory from backups into a new install. Apply your other customizations however those are documented.

[Karthik Bhat]

That helped! Thank you Bob.

[Bob Swift]

GINT - Groovy Integration Test Framework has some JIRA specific enablers. You can use it to test against a test or production instance. You can do better testing against a test instance as Thomas suggest since you can easily create and delete issues, progress issues, and make configuration changes you would not want to do on a production instance. In a production environment, you need some test projects that can be created and deleted. You should also be careful about suppressing notifications for any testing - How to limit notifications for automation actions