You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When a new field is created in a Next-Gen Project with the same name as a custom field in Jira Software, it causes existing filters referencing the custom field to fail.
The existing filters fail because they reference the newly created Next-Gen field, rather than the jira software custom field.
Is anyone aware of this issue? Does anyone have a way to prevent this from happening?
Instead of having the actual field name in your filter, you would need to modify your filter to use the ID instead. For example, I created a field called phone number in a classic project and next gen project. Now, when I do the search, it will give me two phone number field:
So in my case, I would need to change my filter to
project = NH AND cf is not Empty
So it gives me a result. All you need to do is to find out which id is for next gen and which is for classic project. To find out the id, you can go to custom field settings - https://<yourdomain>.atlassian.net/secure/admin/ViewCustomFields.jspa, search for the field, click on ... > Edit details. You will find the id in the URL.
Hope that helps!