Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Next-Gen Custom Field duplication

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? 

1 answer

1 accepted

0 votes
Answer accepted

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:

Screenshot 2020-04-16 at 8.57.58 AM.pngSo in my case, I would need to change my filter to 

project = NH AND cf[10043] 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>, search for the field, click on ... > Edit details. You will find the id in the URL.

Hope that helps!

Thanks Hazwan. 
The only problem is I have many filters already set up, so I would have to go through them all and change them to the field ID. 
Very frustrating. 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events