Managing field overload in JPD across multiple product groups

[J P]

We have started proof-of-concepting JPD by having all our product teams in the same single JPD space (IT IS AWESOME), as we migrate from Roadmunk to Jira Premium with Advanced Roadmaps. 

One of our challenges in JPD specifically is likely a combination of field type availability (labels, dependent dropdowns) +/- making JPD a company-managed project type... It's AWESOME to utilize the flexibility and insight of JPD across all our teams, BUT we also want to figure out how to have certain fields that would be unique to different product groups without having WAY too many fields in JPD.

How are other folks handling or wanting to handle this?

Related posts in this JPD community group:

• Field Types: Are there plans for multiple labels, dependent dropdowns, or other field types? 
• Product Mgt & Engineering Ops: Jira Product Discovery + Jira Software Premium + Advanced Roadmap