You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am administrating a medium-sized Jira Software Server with around 200 projects, 1500 users and a little over 200K issues.
I am often facing requests from project admins to modify the visibility of certain custom field for their project or group of projects they work on.
For example the "Story Points" field - some managers wanted it only for Story issue type, others wanted it for primary issue types (Story, Bug, Feature, Task), third group wanted it for sub-task issue types too, fourth group wanted it for mix of the previous groups,...,you see where I am going.
I know several ways to handle this in Jira
How do you handle such problems?
How do you balance between performance ('cause the number of screens defined in the system is affecting performance of Jira) and maintainability?
Thanks a lot for your input