Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Managing field overload in JPD across multiple product groups

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:

 

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events