Custom field type with key com.xpandit.plugins.xray:requirement-status-custom-field not found

Roy Chapman May 26, 2015

I am trying to transfer a project between instances.  The source instance has the XRay plugin installed for evaluation, the destination doesn't.  The project has no references to this plugin, yet the project transfer fails.  Why should this be if there are no dependencies?

1 answer

0 votes
José Marañón [Awnaba Software S.L.]
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 Leaders.
June 2, 2015

That error is caused because the XRay plugin is not installed in the destination. Take into account that export for one project will include all custom fields, unless you select the option to filter custom fields not used by exported projects. This page of the documentation (https://awnaba.atlassian.net/wiki/display/PCP/Filtering+unused+custom+fields) explains why and explains how the filtering option works, including the criteria to consider when a custom field is "used by" a project.

Consider also that the dependency to a custom field could appear because that custom field is used in a workflow or in a dashboard.

(Due to a problem with Atlassian Answers, this reply was sent directly to Roy a few days ago. I am posting it here so that others can see it too)

Suggest an answer

Log in or Sign up to answer