I have been able to replicate this issue. It only occurs when you have defined a project and/or issue type which does not have the custom field configured to it through the field configuration scheme. Assuming you have assigned the Custom Field to a specific scheme, which in turn is used by a project, you will notice you can both search and select the custom field in question when you leave all other options empty. As soon as you define a project or issuetype to which the Custom Field has not been configured, you will receive the error as you have described.
Thank you so much this helped me. We have schemas for different types of projects. so we have fields that don't apply globally but we actually need them for half our user base - and they are all struggling to complete the filters (alot of gui addicts rather than JQL users). You have saved my bacon! Thanks Mick!
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot