What is the best way to upgrade 3.12 to 5.17 (latest) ? Can you explain step-to-step?

What is the best way to upgrade 3.12 to 5.17 (latest) ? Can you explain step-to-step for easy way?

3 answers

1 accepted

Hi,

I would recommend following the migration procedure:

- https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server

Notice the part: upgrade to JIRA Latest from a version of JIRA prior to 4.0.0 (on the same server hardware and same server environment).

(warning) Please Note: This is a two-step process. Please follow the equivalent 'Migrating JIRA to Another Server' guide (in the JIRA 4.4.x documentation) to upgrade to JIRA 4.4.x first before following the Upgrading JIRA guide (in the JIRA Latest documentation) to upgrade to JIRA Latest. For more information, see the JIRA 5.0 Upgrade Notes.

In a few steps (see documentation for more details):

1. Backup JIRA 3.12

2. Restore to JIRA 4.4

3. Backup JIRA 4.4

4. Restore to JIRA Latest

Cheers,

Pelle

while restore XML backup from 3.13 to jira 4.4.5 we get this error.
Moreover, our log files is here for detailed information  (atlassian-jira.log)

2012-10-31 15:25:41,701 JiraImportTaskExecutionThread-1 ERROR mert 906x113x1 cej0wk 127.0.0.1 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Error importing data: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.jira.util.RuntimeIOException: java.io.FileNotFoundException: D:\Jira\index313\issues\segments_h0k6 (Dosya veya dizin bozuk ve okunamaz durumda)
com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.jira.util.RuntimeIOException: java.io.FileNotFoundException: D:\Jira\index313\issues\segments_h0k6 (Dosya veya dizin bozuk ve okunamaz durumda)
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)
	
Caused by: com.atlassian.jira.util.RuntimeIOException: java.io.FileNotFoundException: D:\Jira\index313\issues\segments_h0k6 (Dosya veya dizin bozuk ve okunamaz durumda)
	at com.atlassian.jira.index.WriterWrapper$1.get(WriterWrapper.java:45)
	at com.atlassian.jira.index.WriterWrapper$1.get(WriterWrapper.java:35)
...............
2012-10-31 15:25:41,795 JiraImportTaskExecutionThread-1 INFO mert 906x113x1 cej0wk 127.0.0.1 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] Importing data is 100% complete...
2012-10-31 15:25:41,795 JiraImportTaskExecutionThread-1 INFO mert 906x113x1 cej0wk 127.0.0.1 /secure/admin/XmlRestore.jspa [jira.bc.dataimport.DefaultDataImportService] JIRA Data Import has finished.
2012-10-31 15:26:08,665 http-8084-3 ERROR      [500ErrorPage.jsp] Exception caught in 500 page null
java.lang.NullPointerException
	at com.atlassian.crowd.embedded.core.CrowdDirectoryServiceImpl.storeLdapConnectionPoolConfiguration(CrowdDirectoryServiceImpl.java:308)

There's not really enough log file here to tell us what's going wrong.

It looks like there's an error in the indexing during import, but that could be fine, as the index should be rebuilt after upgrade. But you then get a Crowd error, which is definitely a problem, but we can't tell what it is.

It works after clear index and i could upgrade 4.4.5 to jira 5.1.8.

Now i am taking dashboard errors for all gadgets.

Are there any suggestion for this error?

Error loading gadget from /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!: org.apache.shindig.gadgets.GadgetException: Unable to retrieve gadget xml. HTTP error 404

I would try restarting Jira quickly, assuming you have re-indexed (although the upgrade should have done that for you as one of the last tasks. You can check by running a search)

If that doesn't help, then you need to check what the gadgets were in 4.4 and find out if they are still valid in 5.1. If they are, then you probably need to check the log file to see what the errors are.

Our log file contains this error log???

012-11-01 17:33:09,069 http-8084-1 WARN anonymous 1053x3x1 4r6y2d 127.0.0.1 /secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!

2012-11-01 17:33:09,803 http-8084-1 WARN anonymous 1053x3x1 4r6y2d 127.0.0.1 /secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!

2012-11-01 17:33:09,819 http-8084-1 WARN anonymous 1053x3x1 4r6y2d 127.0.0.1 /secure/Dashboard.jspa [gadgets.embedded.internal.GadgetUrlBuilder] GadgetUrlBuilder: could not parse spec at /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!

2012-11-01 17:33:09,897 http-8084-1 WARN anonymous 1053x3x1 4r6y2d 127.0.0.1 /secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!

2012-11-01 17:33:09,897 http-8084-1 WARN anonymous 1053x3x1 4r6y2d 127.0.0.1 /secure/Dashboard.jspa [gadgets.renderer.internal.GadgetSpecFactoryImpl] Error occurred while retrieving gadget spec for /invalid/legacy/portlet/Please_remove_this_gadget_from_your_dashboard!

So what are the gadgets you are using?

At 3.13 version system dashbord contains these gadgets.

(Project Gadget,Favourite Filters (Create New | Manage Filters),

Open Issues: In Progress <small>(Displaying 0 of 0)</small>

<small>Open Issues: In Progress <small>(Displaying 0 of 0)</small></small>

)

Do we re-define these gadgets in new version again?

You might have to, yes, although I would have expected a 4.x - 5.x upgrade to update them ok.

Going from 3.x to 4.x would have been a problem, as "portlets" are removed and replaced with "gadgets", so I'd actually understand it if you've gone 3.x -> 4.x, not actually used 4.x because it's just a stepping stone and then gone to 5.x

As you said we get same issue at jira 4.4.5. we make everything according to Migrating+JIRA+to+Another+Server document.

Can we convert existing portlets(defined at jira 3.13) to gadgets?

No. You need to upgrade them to gadgets, there are different parameters and settings to work through.

How can we change login page/dashboard?

After upgrade there is error about gadget on this dashboard

and we want to remove this old gadget.

As you said we get same issue at jira 4.4.5. we make everything according to Migrating+JIRA+to+Another+Server document.

Can we convert existing portlets(defined at jira 3.13) to gadgets?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,240 views 14 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot