Notifications based on User/Group Custom Field Value not being delivered

Still need help?

The Atlassian Community is here for you.

Ask the community


When Creating a Notification Scheme or applying changes to an existing one, it is possible to determine the entity to which a notification has to be sent.
Two options here are the User Custom Field and the Group Custom Field values.

In some cases, it is possible that notifications to particular entities are no longer being delivered

The following appears in the atlassian-jira.log

/secure/CreateIssueDetails.jspa [jira.notification.type.UserCFValue] Error while retrieving custom field. Returning empty list of e-mail recipients. Please remove any invalid custom fields from your notification schemes.
java.lang.IllegalArgumentException: Custom field with id 'customfield_10204' does not exist.


In the example above, notifications sent on the Create Issue Event are not being delivered to a particular entity on the instance, which is determined based on the information in customfield_10204.
In this case, the custom field in question does not exist. This can be validated by looking up the field in the database:

select cfname from customfield where id = 10204

The value found with the query above will help determine whether or not the custom field is still present on the instance on the Custom Fields page.
In this case, it will not be possible to find any custom fields with the name found in the database query.


The custom field as found under the diagnosis is not present anymore on the instance.
This can be due to a manual removal of the field, or uninstalling/disabling an add-on which created the custom field. 


In order to prevent the error in the logs from surfacing, remove the User Custom Field or Group Custom Field values from your notification schemes.

In order to ensure the entities receive the notifications again:

  • Recreate the custom field
    • Ensure the newly created custom field is used in your notification schemes instead of the old one.
      Bear in mind that Screens might require adjustment to refer to the proper custom field as well.
      The same goes for Workflow configurations
  • Enable or reinstall the add-on responsible for creating the custom field
Last modified on Nov 2, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.