Couldn't update fields for "Task" issue type

[AY]

Hi!

I'm trying to reorder fields for the "Task" issue type, but I received an error "Sorry, something went wrong and we couldn’t update your “Task” issue type."
The same happens when I try to add new fields.

For "Bugs" and "Subtask" it's works fine.

This is configuration issue and I need to edit it in some other way or it's a Bug?

[Andy Heinzer · Accepted solution]

When this error happens, take a look into the browser's developer tools.  If you can navigate into the response, I expect there will be an error code, like this one:

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"

In which case, the Original Estimate field cannot be saved into the Description Field types.  If that is the error in your browser, try moving this down to the Context fields instead and save. If your browser errors on a different field, perhaps try moving that instead.

If your browser mentions some other different error, please share it.

[Lana Moore]

This issue is still recurring for me on most of my issue type fields. I am prevented from further organization of our issue types. Is this close to being ressolved?

[K M]

Hi, 

I have the same error but my fields look a bit different:

I also have the following error:

I created the structure of this issue type a couple of days ago but today I decided to add labels into "Labels" - it refused to save.

[Andy Heinzer]

Hi,

Sorry to hear about this problem.  I have created a bug ticket based on the behavior here.  Please see https://jira.atlassian.com/browse/JRACLOUD-79684

It would appear that some sites are not allowing this custom field to be placed within the Description section of the issue type.  The work-around for the time being is to move this field to the context section. However I would recommend watching that bug ticket for updates

[Ivan Tan]

This issue still with me, when I'm trying to update filed in both "Task" and "Story" issues, unable to save my changes

[John Funk]

Hi Ay - Welcome to the Atlassian Community!

Do you get an error if you change the order or add a field directly on the screen? 

Also, what type of project is it? 

[AY]

Hi John!

This was a Kanban project, and yes, the error occurred whenever I tried to change (reorder or add) fields in Issue Type (only for Task)

Anyway, I tried to do it today and it works to me. A bit strange but I'm happy that it works now)

Thanks for your time

[John Funk]

Great! Glad it is working for you now. 

[vishnu]

this issue still exists for me, i am trying to add priority filed to the issue type bug

[John Funk]

Can you provide more details please?

[John Funk]

We need more details please. 

[Zdravko]

Its a Kanban project type and adding any field onto tasks (like priority or start date) and then saving the changes with the "Save changes" button in the lover left throws out and error that says "Couldn't save your changes". I'll include the error message and the console error message. basically its an error 400. If you need more information, I'll gladly provide it.   

[John Funk]

This is exactly what Andy's response was above. You cannot have the Original Estimate field in the Description fields section. You must move it to the Context fields section to not receive the error. 

[K M]

Hi John, how to move fields? If I'm dragging a field from the Description section the only option I have is to remove it.