Version 3.3.3 is not importing Version 2.6.4 data

[Kevin Salt]

Just doesn’t work. I am migrating from Jira v5.2 to v6.4 and Scheduler-Pro V2.6.4 to v3.3.3 and I have followed the instructions on your wiki page carefully and even tried several interpretations of your instructions but none work.

3.3.3 creates the TSP_QRTX_* tables but does not read theschedulerdb.script and/or populate the tables.

There is no traceback, no warning, nothing in the logs, and everything continues to run perfectly. I can import exported issues from another 3.3.3 instance. However attempts to export from a 2.6.4 instance results in a stack trace and an Type cast error attempting to cast an array as a set - I would report this as a bug but it is in an outdated ad unsupported version.

[Łukasz Modzelewski]

Hi Kevin,

We received your email earlier and we are currently investigating this issue.

Please be patient version 2.6.4 is very old and we are close to releasing version 5 ;)

I'll update you on progress.

Best regards,

Łukasz

[Łukasz Modzelewski]

Hi Kevin,

we have managed to fix the issue with import in your version, please download "theschedulerpro-3.3.4_i179.jar", install it from file and try again.

It will work but you need to know that earlier version of The Scheduler was not saving the name of the scheduled issue - that is why it will be filled it with summary of the issue. This should be descriptive enought to allow you to easily find and edit right issues. If you encounter any problems we will do our best to help you.

Let us know if it helped.

Best regards,

Łukasz

Btw. Please consider upgrading Jira to 7.x version - because official support for 6.4 ends within 2 weeks https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html

[Kevin Salt]

Thanks Łukasz - Yes I'm doing the 5.2 to 6.4 upgrade so that i have the way clear to do the 6.4 to 7 upgrade in a few weeks time ... Also trying to get everything a little more "factory" in the installation I inherited.

I'll get back with another comment as soon as i have tested the new version you provided.

Cheers

Kevin

[Kevin Salt]

Nope .. still no joy I'm afraid .. the plugin installs cleanly, but the [JIRA_HOME]/data/plugins contents remain untouched, and checking the project admin shows no scheduled tasks in the Scheduler Statistics. I am assuming that the plugins directory should be where it was when we were running V2.6.4 ... i.e. the place where Jira keeps its data, in the data/plugins directory .. even though your instructions refer to bin/data/plugins ... (I also have a sim-link to data/plugins from bin/data/plugins ..

I'm now completely lost ...

[Łukasz Modzelewski]

I'm sorry there was some confusion - don't follow documentation. It's a bit outdated - due to big changes in database.

Here is what you need to do right now:

1. Export your issues from old jira and old Scheduler -> nagvigating to the page from screenshot_1

2. In new jira 6.x import issues using import module as you can see in screenshot_2

Issues will be imported with changed names as I mentioned earlier.

Future plugin updates are smoother and don't require any interference from user part.

Let us know if this helped.

[Kevin Salt]

Ahaa ... That is also not possible Łukasz .. When I try to export from the old instance which still uses 2.6.4 I get a stack trace ... As soon as I can get back inside the VPN I'll copy/paste the top few lines, but the exception thrown is an attempt to cast an array as a set ...

[Kevin Salt]

Cause: java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.util.Set Stack Trace: [hide] java.lang.ClassCastException: java.util.ArrayList cannot be cast to java.util.Set at com.atlassian.jira.issue.fields.LabelsSystemField.validateParams(LabelsSystemField.java:219) at pl.com.tt.jira.plugin.thescheduler.action.issuescheduler.BackupSchedulerDataAction.backup(BackupSchedulerDataAction.java:463) at pl.com.tt.jira.plugin.thescheduler.action.issuescheduler.BackupSchedulerDataAction.doExecute(BackupSchedulerDataAction.java:304) at webwork.action.ActionSupport.execute(ActionSupport.java:165) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:221) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:150) at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) ... ... ... etc ...

I can copy/paste the lot if you need it

[Łukasz Modzelewski]

Ok, there is another thing we could try: upgrading step by step.

Please try upgrade to version 3.0.3 following the documentation.

You can download it from here: https://marketplace.atlassian.com/plugins/pl.com.tt.jira.plugin.theschedulerpro/versions

[Kevin Salt]

I already tried that Łukasz ...

In the end I ran out of time so the engineers will have to re-enter their scheduled tasks by hand ... In May/June we will upgrade to Jira 7 and Confluence 6 so I think we can let this issue close itself.

Thanks for all the attention and support