nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to resolve "Cannot get property 'query' on null object" in project configurator plugin?

Shriya Chhajed

I am facing this issue while exporting a project in jira:

"Cannot get property 'query' on null object"

I face this issue when i select the option "Shared with exported projects " in Filters to export and Dashboards to export.

Error (JIRA).PNG

My jira version is 7.3.8 and i am using jira configurator plugin to export a selected project in jira.

Please help me to resolve this issue.

Thank you

Accepted answers

Kristian Walker _Adaptavist_

Hi Shriya,

Thank you for your question.

I can confirm that the error message above indicates that an agile board is being exported from the source instance which does not have a filter configured for it, as the filter associated with it has been deleted.

The workaround for this issue is to identify the agile board or board(s) which have an invalid filter which you can do by running the SQL query below in the JIRA Database on the source instance.

select b.NAME, b.SAVED_FILTER_ID, f.filtername, f.reqcontent 
from AO_60DB71_RAPIDVIEW b left 
join SEARCHREQUEST f on b.SAVED_FILTER_ID = f.id 
where f.id is NULL;

Once you have identified the board with the missing filter you can then either remove this board or update it to use a new filter which exists before taking a new export to import from. The Atlassian article located here outlines how you can associate a new filter to the invalid board inside the database.

We are currently working on improving the message thrown when this error occurs and plan to release these improvements within the next version.

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.

Regards,

Kristian

All comments

EvyL

I'm having the same issue today when trying to export a project using the Jira Configurator Plugin.

Kristian Walker _Adaptavist_

Hi Shriya,

Thank you for your question.

The workaround for this issue is to identify the agile board or board(s) which have an invalid filter which you can do by running the SQL query below in the JIRA Database on the source instance.

select b.NAME, b.SAVED_FILTER_ID, f.filtername, f.reqcontent 
from AO_60DB71_RAPIDVIEW b left 
join SEARCHREQUEST f on b.SAVED_FILTER_ID = f.id 
where f.id is NULL;

We are currently working on improving the message thrown when this error occurs and plan to release these improvements within the next version.

If this answer has solved your issue can you please accept it in order to mark this answer as correct for users who are searching for a similar issue.

Regards,

Kristian

Shriya Chhajed

Hi @Kristian Walker _Adaptavist_

Thank you for your reply.

Currently I am able to export the project using some other configurations. But now I am facing the issue while importing the same project.

When I try to import the project, I exclude some of things like Users, Groups, Custom Fields, Field Configurations, field configuration schemes, Scrum and Kanban boards. But when I start importing it, it shows the error (see attached screenshot)

Does issue types/fields etc doesn't gets override when we import the project and if already exists in destination Jira?

Currently it is showing of one issue type named "Test", but later when it gets resolved it might show the error for other fields. Do we have any work around for this? Can you please help?

Thanks and Regards

Shriya Chhajed Jira import error.PNG

Kristian Walker _Adaptavist_

Hi Shriya,

I can confirm that the error shown in the screenshot above indicates that there is already an Issue type of Test inside of the target instance that you are importing into.

Issue type names are case sensitive so an issue type with the same name in a different case such as 'test' would be classed by the importer as the same issue type.

Also Standard and Sub-Task issue types can not have the same names meaning if you are importing a standard issuetype and their is a sub task with the name of test then you will get this error.

The workaround for this error is to review the issue types in the source and target instance and to update the names to the same case if the issue types are the same type, or to rename one to be unique if they are of different types.

Once one of these actions has been taken then a new export should be taken from the source instance to import from.

Regards,

Kristian

Shriya Chhajed

Hi Kristian,

Thank you so much. That helped us and now we are not facing the same issue

Thanks and Regards

Shriya Chhajed

Hi Evy,

Please try the same solution. I hope that will help.

If not, then please post the screenshot of your error with details.

Thanks and Regards

Shriya Chhajed

Hi Kristian,

There is an another issue which i am facing while importing the project. This time i am importing all the projects from one instance to the another. And like before i am skipping the users, groups and boards while importing and using the same options as before.

Please find the attached error which i am facing, which is something related to corrupt zip file i think. Please suggest.

Thanks and Regards

Shriya Chhajed jira import issue.PNG

Kristian Walker _Adaptavist_

Hi Shriya,

The error inside your screenshot above indicates that the Zip file being imported is corrupted which could of happened during the data transfer from the source instance to the target instance.

In order to validate the file could you please check the following.

That the file contains an extension of .zip on the target server.
That the file can manually extracted using a Zip tool such as 7Zip.

If the file cannot be successfully opened then you will need to take a new export from the source instance and transfer this to the target instance to import from.

Regards,

Kristian

Shriya Chhajed

Hi Kristian,

I tried doing both the things:

1. yes it contains the .zip extension at target server

2. When i try extracting it using 7Zip, it reached till 100% to unzip the file but at last it shows "Headers error"

Also tried creating the new export file from the source instance, but the same error occurs while importing it in target instance. There is no error while exporting it when in source instance.

Can you please suggest the workaround for this error, i am stuck with this and not able to complete it.

And also is it possible if i remove the Attachments folder before exporting it (because the path specified in the error is something related to attachment, though not bale to get the exact file location), so that this error can be resolved?

Thanks and Regards

Shriya Chhajed

Kristian Walker _Adaptavist_

Hi Shriya,

Thank you for your response.

We believe that this error is being caused by a corrupt attachment inside the attachment directory being backed up, and that this attachment is causing your export to fail.

To work around this you could take a copy of the source instance without attachments over to a local server to take the export from.

Regards,

Kristian

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

addon-com.awnaba.projectconfigurator.projectconfigurator