Official release: Jira 8.16 and Jira Service Management 4.16

Hi @tbartyzel,
thank you for the heads up!
With the release of 8.16 we are also experiencing another strange behavior regarding custom fields in addition to the previous fixed one mentioned in this blog post:
In our custom fields we are extending from EditCustomFieldOptions. We have implemented the setter setCustomFieldId(Long customFieldId) which used to work in prior versions (the method was invoked via reflections by the JiraSafeActionParameterSetter). But since Jira 8.16 it seems as if customFieldId is no longer available in this context and therefore the setter won’t be invoked anymore.
Could you maybe check, whether this is on purpose or if this is actually a bug at this point?

Thank you!
Cheers :slight_smile: