Versions and Components are not required to import?

Project Import tool requires versions and components to be empty. So do we need to restrict importing versions and components with Project Configurator?

1 answer

Yes, you should skip import of components and versions.

When you are about to import the project configuration, select to skip "Versions" and "Components" in the "Do not load" window of the "Project configuration file upload" page, so that they are not created in the new project. You can find a complete description of the process here: Moving a project to another instance.

So what happens if the filters has components or versions? While importing we observed below error. Is it related?

Log Trace

2016-02-29 18:18:10,476 http-bio-8080-exec-16 INFO hgunturu 1098x22735x1 1e0yus3 10.16.37.144,10.15.160.174 /secure/project-config-file-upload.jspa [projectconfigurator.loaders.core.AbstractIntegratedHandler$1] Creating filter No component set, not closed by amorgan 2016-02-29 18:18:10,477 http-bio-8080-exec-16 WARN hgunturu 1098x22735x1 1e0yus3 10.16.37.144,10.15.160.174 /secure/project-config-file-upload.jspa [projectconfigurator.loaders.handlers.ProjectConfigLoader] An error was detected during the import

Load failed for reason: com.atlassian.jira.jql.parser.JqlParseException: com.atlassian.jira.jql.parser.antlr.RuntimeRecognitionException: NoViableAltException(59@[])
An error occurred during the load: Load failed for reason: com.atlassian.jira.jql.parser.JqlParseException: com.atlassian.jira.jql.parser.antlr.RuntimeRecognitionException: NoViableAltException(59@[])
WARN  18:18:10,477 An error was detected during the import com.awnaba.projectconfigurator.utils.errorhandling.XMLInputDataException: com.atlassian.jira.jql.parser.JqlParseException: com.atlassian.jira.jql.parser.antlr.RuntimeRecognitionException: NoViableAltException(59@[]) at com.awnaba.projectconfigurator.jiraobjectfacades.FilterToolsImpl.parseJQLQuery(FilterToolsImpl.java:255) at com.awnaba.projectconfigurator.jiraobjectfacades.FilterToolsImpl.createFilter(FilterToolsImpl.java:242) at com.awnaba.projectconfigurator.loaders.handlers.SearchRequestHandler.createNewTargetFrom(SearchRequestHandler.java:39) at com.awnaba.projectconfigurator.loaders.handlers.SearchRequestHandler.createNewTargetFrom(SearchRequestHandler.java:22) at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler$1.createNewFrom(AbstractIntegratedHandler.java:187) at com.awnaba.projectconfigurator.loaders.core.AbstractSmartCreator.smartCreate(AbstractSmartCreator.java:13) at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.shallowCreate(AbstractIntegratedHandler.java:202) at com.awnaba.projectconfigurator.loaders.core.AbstractIntegratedHandler.createTarget(AbstractIntegratedHandler.java:160) at com.awnaba.projectconfigurator.loaders.core.AbstractTargetHandler.handleTarget(AbstractTargetHandler.java:100) at com.awnaba.projectconfigurator.loaders.core.AbstractHandlerWithErrorRecovery.handleTarget(AbstractHandlerWithErrorRecovery.java:15) at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.loadGlobalCollection(ProjectConfigLoader.java:412) at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.loadGlobalObjects(ProjectConfigLoader.java:201) at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.loadOperations(ProjectConfigLoader.java:125) at com.awnaba.projectconfigurator.loaders.handlers.ProjectConfigLoader.doLoad(ProjectConfigLoader.java:77)

Error Message

An error occurred during the load:
Load failed for reason: com.atlassian.jira.jql.parser.JqlParseException: com.atlassian.jira.jql.parser.antlr.RuntimeRecognitionException: NoViableAltException(59@[])

 

 

Hi Srinivas,

Having a look at the query for that filter would clarify the reason for this problem. The filter query can be found in the "<query>" element of the filter description in the XML file. The fastest check would be pasting that query into the advanced mode window, in the JIRA page "Search for issues", and see if that query is rejected and why. Sometimes, simply the examination of the query string is enough to find out why it cannot be parsed correctly.

Thus, this issue need not be related to the fact that project components do not exist yet. If it were related, the best course of action would be:

  • import the configuration skipping versions, components, filters and dashboards
  • import project data with JIRA Project Import Tool
  • import the configuration skipping everything, except filters and dashboards

Cheers!

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

631 views 4 15
Read article

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