Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I use a custom field from a classic project in a next-gen project? Edited

This is actually getting quite annoying because when I am trying to create a custom filter/search, I see a field with the same name n times in the 'columns' list depending on how many next-gen projects are using the same field name. There is no indication of which field belongs to which project so no way for me to know.

The field names could probably have been auto-suffixed with the project key in the columns list.

Any suggested workarounds?

1 answer

0 votes

Hello @Chetan Singh

Thank you for reaching out.

Unfortunately, it is not possible to share the same custom field (From a Classic or Next-gen project) between multiple Next-gen projects.

This behavior happens because the architecture of Next-gen projects was designed to use unique entities (Fields, issue types, statuses, etc) on a per-project basis, with the future goal to enable the migration of single projects between multiple Jira Sites. You can check more information about this in the documentation below:

Jira Cloud next-gen projects and the effects on the REST API 

That being said, we completely understand that a big amount of Next-gen projects will cause the JQL queries to return a huge amount of custom fields, which can be very confusing when using similar names. With the awareness that this feature must be improved, we created the following feature request:

As a Jira next-gen project admin, I want to be able to use the same custom fields in different next-gen projects 

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,251 views 10 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you