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

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 9.3.0
    • Affects Version/s: 9.0.0, 9.1.0
    • Component/s: Custom fields
    • 9
    • 3
    • Severity 3 - Minor
    • 4

      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

        1. image (2).png
          image (2).png
          43 kB
        2. image (3).png
          image (3).png
          28 kB

            Assignee:
            Karol Skwierawski
            Reporter:
            John Vecchio (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: