Custom field limitation

Hi,

I would like to know that is there any limitation of  having custom fields in default screen. For example, We want to customize "create issue" screen by adding around 30 to 50 custom fields approximately and we might need to remove some unwanted default fields provided. 

As per my understanding custom fields are being stored in jira's custom table (the one which is used for customfields). Is there any way to extend the table which is being for storing issue details? If not so, can we store them in custom table and can we pull those values from that table for reporting purpose? 

 

1 answer

0 votes

50 custom fields is not going to be a problem for JIRA

(But it's not going to be nice for your users.  Even if it's just one project or even issue type, you're going to find the field names leak out into searches and your users, when faced with 50 fields, will tend to leave as many of them as empty as possible)

For the second part of your question, the answer is generally "no".  You don't want to try to do this the hard way, by messing with JIRA's database.  Write a new custom field plugin and let that handle it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,941 views 19 22
Read article

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