Log warning "There is not exactly one config for this scheme ({}). Configs are {}.".

[Mark Jansen]

Hello,

We have an Jira server app in the marketplace called "edit custom field values". A client of ours gets the following warning "There is not exactly one config for this scheme ({}). Configs are {}." when interacting with our app.

I have since determined that this has to do with calling the following Jira function in the class `FieldConfigSchemeImpl.class`.

@Nullable
public FieldConfig getOneAndOnlyConfig() {
  MultiMap configsByConfig = this.getConfigsByConfig();
  if (configsByConfig != null) {
    if (configsByConfig.size() == 1) {
      return (FieldConfig)configsByConfig.keySet().iterator().next();
    }

    log.warn("There is not exactly one config for this scheme ({}). Configs are {}.", this.id, configsByConfig);
  }

  return null;
}

Apparently our client has more than one field configuration in a scheme, which causes the function above to return a null value that causes a problem the code of our app.

I have difficulty reproducing the issue our client is experiencing. I'm unable to get more than one field configuration in a scheme.

Does anyone know how I could get this done? Or how to make is so our client doesn't have two configurations for one scheme?

I have already tried to create a field configuration scheme and field configurations in settings > issues.

If there are gaps in the information I provided, let me know and I'll elaborate.

Thanks in advance.

[Brant Schroeder]

@Mark Jansen Welcome to the Atlassian community.  Sounds like something got corrupted.  I would suggest submitting an issue to Atlassian support. https://support.atlassian.com/contact/