When using the translate option for a custom field, Jira throws a HTTP 405 - Method Not Allowed

Issue Summary

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Create a custom field in Jira
2. Click on the translate options
3. Select any language
   

Expected Results

Page renders normally and performs the translate

Actual Results

The below exception is thrown in the xxxxxxx.log file:

2022-08-02 17:51:33,191+0000 http-nio-8080-exec-151 ERROR      [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] threw exception [com.atlassian.jira.util.dbc.Assertions$NullArgumentException: item should not be null!] with root cause
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: item should not be null!
	at com.atlassian.jira.util.dbc.Assertions.notNull(Assertions.java:25)

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available

Note

Internal testing on Jira v8.22.X did not reproduce the issue