Jira log filled with warnings Did not find requested custom field

[Steve Kamens]

I'm seeing a warning filling up my log file saying: 

[c.o.s.c.jira.utils.LazyCustomFieldsMap] Did not find requested custom field <Custom Field Name>

in response to a simple API call to retrieve the issue: /rest/api/2/issue/DERF-1088, for example.

That custom field is configured only for Epics and the issues being requested are not Epics

Why is that field being requested when it shouldn't be and how can I stop that from appearing.

[Angélica Luz]

Hi Steve,

I saw that you created a ticket with our support related to the same question, so to avoid any possible misunderstandings or miscommunication that may arise from discussing the same matter in two different platforms, let's focus on the ticket instead.
Once the ticket is resolved, feel free to share the resolution here to help other community members that may face the same issue.

Regards,
Angélica

[Ramakrishnan Srinivasan]

Hi Steve,

I have the similar issue, can you please share the issue number, if possible I can add my observation there

Thank you

regards

ramki

[Steve Kamens]

The issue was that a ScriptRunner Listener was trying to get the value of that field on an issuetype that is not configured to have that field.

I fixed it by checking the issuetype in the listener and only looking for the value on issuetypes that are known to include that field.

The issue GHS-154627 is Resolved, since it turned out to be a ScriptRunner thing.

[Ramakrishnan Srinivasan]

Hi Steve, 

 Thank you very much, it will really help me because my log file has grown really big because of this. Let me attack my listeners now, 

with warm regards

ramki

[Daniel Garcia]

What did you mean by "not configured to have that field" ?