Summary

Once a Next-Gen project is created in the cloud site and if more than one new scoped custom field is created with a similar name to the global custom field it becomes confusing to JQL query an Advanced Search.

Environment

• Cloud

Steps to Reproduce

1. Create a Next-Gen project
2. As a Jira admin, check the list of custom fields in your site through /secure/admin/ViewCustomFields.jspa
3. Let's get for example the custom field that I have on my test instance named Business Line:
   • 
4. Go to the newly created Next-Gen project and created a custom field with the same name
   • 
   • Don't forget to save!!
5. Again, this time, create a new Next-Gen project
6. Again, create another custom field with the same name in this newly created project
7. Now, go to make an Advanced Search
8. It is extremely hard to differentiate between these fields:
   • 
   • An end user is not supposed to know the id of each custom field.
   • Imagine for someone who has 35 Next-Gen projects for example on his site.
   • Imagine for someone trying to choose between two custom fields that are both related to Next-Gen project

Expected Results

• It easy to identify which value to choose from during making the "Advanced Search"

Actual Results

• if there were only two values we can identify that the first value is related to a global custom field and the second one is related to a scoped custom field. However, It is confusing to find more than two values with the same name.

Workaround?

• A workaround would be to verify the id
• Or, choose a different name