How are you managing your Next Gen projects?

[Jeanne Howe]

We have spent a great deal of time setting "standardized" schemes in JIRA. This ensures teams and projects are using the same basic methodologies for tracking their work. It also helps to ensures we can meet strict regulations for requirements traceability and auditing.

With Next Gen projects, users are able to create their own workflow status, issue types, and custom fields. This results in multiple objects with the same name, e.g custom fields, workflow status, issue types, and/or multiple objects that mean the same but are labeled differently, e.g. To Do vs Ready for Development

How would one go about gathering metrics and reporting against work when every project has its own "standard"? 

How do you prevent duplication of objects?

How do you find and remove "abandoned" projects as well as the custom objects that were created for the projects?

[John Wilson]

We've created many standardized schemes as well. To keep them safe, we have disallowed anyone except jira admins from creating next-gen projects. We might open them up to teams that are truly independent, but in general, we need to keep any team for which we need standard reporting metrics in our standard schemes.

[Jeanne Howe]

We have also disallowed the creation of next-gen projects, for those same reasons.

Leaves me curious to understand when, and why a next-gen project would be used.