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

[vicky]

I'm using a Classic project for my Engineering team, and a Next-Gen project for non-engineering triage (for customer support, marketing, etc. to enter requests and problems, and for product management to triage the problems there in a simple way before they are moved to the classic engineering project with more complex, standardized workflows).

I have a couple of custom fields created in the Classic project that are required for our Engineering workflow (ex: company department, product feature). I'd like to also require these custom fields in the Triage project, but manage the fields in one centralized place, to ensure the same options are in the dropdowns for those fields.

Is this possible? I don't currently see any way to associate the custom fields to the issue types from the next-gen project.

[vicky]

Interesting, thanks for the responses! I was hoping to use the Classic Project for our Engineering team, and Next-Gen for customer support triage, product planning, etc. However, I will eventually have to move issues from the support/planning boards to the engineering board, so it's important for certain fields to be shared. It sounds like what I was trying to do is not possible, so I will need to use Classic projects for everything.

Is it safe to assume that Classic projects will always stick around and will not be fully replaced by Next-Gen projects in the future? The simplicity of Next-Gen projects is attractive, but does not meet the needs of more complex engineering workflows.

[Angélica Luz]

Hi Vicky,

Currently, there are no plans to remove classic projects and if it happens, administrators will receive an email informing this.
Next-gen projects were created to simplify the onboarding for new users and we know that classic projects are very important due to the features that it has, so you don't need to worry about because we will have classic projects for a long time.

Regards,
Angélica

[Angélica Luz]

Hi Vicky,

Next-gen are independent projects, so it's not possible to use custom fields created for classic projects on next-gen or use the next-gen fields on classic projects.
Next-gen has system fields like summary, description, for example, and then the other fields are created directly in the project and you must add fields for every issue type.

We don't have a feature request specifically for that but we have a feature suggesting the ability to add more type of fields on next-gen projects:
- https://jira.atlassian.com/browse/JSWCLOUD-17266
Please, click on vote and watch to receive updates about the features.

Regards,
Angélica

[Petter Gonçalves]

Hello Vicky,

Thank you for raising this question.

Unfortunately, You are correct to say that the custom fields of Classic Projects are not applied for Next-Gen Projects.

In fact, Next-gen projects were created to provide simple functionalities for teams which do not need the complexity of JIRA software as Contexts for Custom fields, Field Configuration Schemes, etc.

That being said, next-gen projects have almost all features specially developed for it,  Including Custom fields. So it can not be shared with other project types and vice-versa.

Additionally, our development team is still working to implement all custom fields types available in the Classic Projects for the Next-gen platform too as you can see in the feature request below:

- Custom fields for Next-gen project

Please, let me know if the information above clarifies your question.