Issue Summary

Multiple users have reported being unable to make changes to an issue type within team managed project. When trying to do so, the browser throws an error such as

Couldn't save your changes
Sorry, something went wrong and we couldn't update your "Task" issue types.

Steps to Reproduce

1. This only appears possible to reproduce within Jira Cloud environments that had the Original Estimate field listed within the Description Fields section on or before August 5th, 2022.
2. If that field exists on the issue type in that location, no other changes will be able to be saved to that issue type

Expected Results

• We expect that the issue type will be saved
• Should the issue not be saved, it would be more helpful to throw a more visible error to the end user
• If users are not permitted to place that field in that location, then it should never appear there

Actual Results

1. Browser session throws a popup card error of

   Couldn't save your changes
   Sorry, something went wrong and we couldn't update your "Task" issue types.

2. Inside the browser's devtool / browser console, we can see there is an HTTP 400 request being made with the response of

   XHR PUT https://[redacted].atlassian.net/rest/internal/simplified/1.0/projects/10187/issuetypes/10624
   [HTTP/2 400 Bad Request 368ms]
   errors	Object { "Original estimate": "cannot be moved in to the content category" }
   Original estimate	"cannot be moved in to the content category"
    
   

Workaround

Moving the Original Estimates field into the Context field types instead allows the issue type to save the changes.