I resolved above mentioned error,
That's not unusual - a broken custom field may throw errors in places where it's read or referred to, not necessarily just when you are configuring add-ons or fields.
What type of field is it?
By "where is it coming from", I meant what add-on are you using to provide it, but I apologise for not making that clear at first.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events