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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


How to stop when a custom field is added, it gets added to all field configurations

When admin's of our JIRA instance adds custom fields to our instance as the use cases of using JIRA grows, one of the key observations is that the custom fields added are also added to ALL field configurations that are setup.  Meaning, those that spent the time at time of project creation to complete a field configuration for the custom fields that matter to the project, are expanded everytime someone adds a new custom field.  This impacts what shows up in Bulk, what data is stored (especially when default values are set on the new custom field) as well as what gets exported with "All".

I'm tired of ALWAYS going to reconfigure field configurations for the projects I administer when other members of the Admin team are expanding the use of the platform.

Is there a better way, or a setting to stop this behavior?

1 answer

0 votes
Ollie Guan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 12, 2018

Hi @Brian Kohler,

I do not know whether similar permission control can be done through configuration and plugins. We have encountered similar problems before, and we adopted the following solution:

1. Limit the number of administrators
2. When an administrator creates a new field, it is associated with a specific IssueType and Project. Do not apply to the global.

David Harkins
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 19, 2023

Hi @Brian Kohler 

Have you been able to find a Solution to this?

Having the same issue here, multiple business departments in our instance and both Development ad Service Management.

Bulk Edit screens become longer and longer.  Users notice the fields and start using them because they are there. only to raise issues when they disappear. 

With near to 50 Field Configurations, it can become time consuming keeping them all in check.

Suggest an answer

Log in or Sign up to answer