best practice for custom fields?

We use a lot of custom fields for our projects and usually those fields are specific to certain projects, but not always. Is there a best practice around custom fields/configs and also later removing the fields from screens? I could just remove the field from the screen, but then if I later audit the custom fields I can't tell which ones were actually in use before. Should I just hide them in the config? Each solution I come up with has additional questions. So, is there a best practice?

1 answer

1 accepted

0 votes
Dieter Community Champion Oct 25, 2012
As Jira is currently implemented you should avoid too many field configurations and create more screen schemes instead. Please read this I hope this will be fixed soon. Please consider to vote there also.

Thanks Dieter. We'll use that as a starting point :)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,868 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot