Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Nest a group via Groovy using script runner

Carlos David
Contributor
October 27, 2017

I've enabled Nested groups in jira, but now wish to nest AD groups within jira groups with groovy (via the Script Runner console).

 

groupService.addGroupsToGroups() 

does not work via the Script Runner console, no error message is provided

1 answer

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 11, 2013

Depends on how you are doing 3.13 to 4.4.

If you're exporting the XML and then importing it, then no, 4.4 will create the correct database layout and import the data.

If you are pointing the new 4.4 at the existing 3.13 database and expecting it to do all the work, then yes, you need to follow those instructions - shut down 3.13, take a backup of the database, run the scripts and alterations, start Jira 4.4

Two pretty obvious points here, but I've seen people skip them and create nightmares. 1) Test it properly on non-production systems before you start and 2) Backups. Database backups are your friend. Be nice to them...

Johann NG
April 11, 2013

Ok, I got it. No shortcuts for database upgrade.

Of course everything will be tested until it is safe do final upgrade in production.

Thanks!

Cheers

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 11, 2013

It is only because there are column format changes between 3.x and 4.x and the code in Jira doesn't cope with those changes. Fortunately they are actually reasonably simple (heck, I can follow the script, and my DBA knowledge is little more than "select from where"). A clean install followed by import of xml bypasses the problem because it creates the columns in the right format, but that's not always the right answer for every situation.

Fortunately, you'll find 4.x to 5.x has nothing anywhere near as scary in it :-)

Johann NG
April 11, 2013

Thanks Nic for your feedback.

I read JIRA Upgrade Guides from 4.0 to 4.4.5.

It seems that there is only one Oracle script to apply when upgrading from 3.13.5 to 4.0

This not a big deal indeed.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events