Hi Team,
We are migrating from JIRA Data Center to Atlassian Cloud and planning not to migrate any custom fields due to performance issues and cost of maintenance of Custom field.
But i think e can have few custom fields not many, please suggest
Yes, every custom field creates overhead, in rendering, search and storage.
In Jira, the load imposed by this overhead is broadly linear - each additional field adds the same amount of load. But for your humans, it's more exponential 20 fields is not twice as much work as 10, it's more like 3 times the work, 30 fields is ten times the work.
On the server side, you can reduce some of the impact by limiting field context - only allow them in the projects that need them. (Screens and field configurations do not help here, it is only context that helps)
On the human side, stop making their life hard - minimise the number of fields they have to put data into, avoid using the "mandatory" flag as much as possible, and automate usage of the fields as much as you can (calculated fields are your friend if you have complicated data)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.