global field not available in next next project

[Stefanie Sullivan]

A custom field ( Single Select picklist ) was created and added globally but I do not see it in my next gen project. How do I get a global picklist to appear across all my projects regardless of the type of project?

[Ravya Mutyala _Appfire_]

Hi @Stefanie Sullivan ,

I guess one of the fundamental characteristics of NextGen projects is that they are unique and nothing you do to one project will have any impact on any other project (NextGen or Classic). 

I saw an existing ticket with Atlassian for sharing the configurations, please refer the ticket:

https://jira.atlassian.com/browse/JRACLOUD-71712?_ga=2.162266677.885920603.1572848122-1372120514.1552382236

Maybe you can also refer to the roadmap of Next-gen project here, they are planning for lot of things incoming 2020, which includes "Share next-gen project configurations and workflows": https://www.atlassian.com/software/jira/whats-new/next-gen#result-3d7aca64

--Ravya

[Stefanie Sullivan]

That's unfortunate. Can I convert my existing next gen project to a classic project template?

If not what would be the recommended path for moving from Next Gen to Classic?

Create a new classic project and then just move all the jiras there?

[Ravya Mutyala _Appfire_]

Hey @Stefanie Sullivan ,

You may refer to the article Migrate between next-gen and classic projects from the below link., you can't "migrate" precisely in that there is no 'button' to migrate. However, you can move all issues from the classic project to the next-gen. Depending on the complexity of the workflow on the classic you will need to map the status to the more streamlined next-gen but the Move will walk you thru it.

https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-next-gen-project-to-a-classic-project-957974933.html?_ga=2.169637160.885920603.1572848122-1372120514.1552382236

--Ravya