task_history.action is incorrectly updated to 'RELEASED_FOR_MAPPING' when a task is locked

[spwoodcock]

Describe the bug

• When a task is locked via the frontend, the database value in task_history.action is updated to RELEASED_FOR_MAPPING.
• This is either a frontend or backend issue, incorrect use of an enum value. I think a value of 0 is used when we probably need to pass 1 to lock the task.

To Reproduce

• Lock a task
• Check the db

Expected behavior

The task_history action value is updated to LOCKED_FOR_MAPPING.

Screenshots

As you can see in the screenshot, the action_text is correct, but the action value is wrong.

[manjitapandey]

I am still having this issue of not being able to mark task as more mapping needed during task validation. Are we on same issue or i understood the issue differently.
unable to update task error message is shown with 500 error on network panel. View image

[spwoodcock]

Let us know if PR 1618 fixed this @manjitapandey 👍

[manjitapandey]

I am restricted to test this issue because of #1657

[manjitapandey]

Encountered an issue while the task is validated. The pop-up still shows locked for validation. The state of pop-up is not updated.

cc: @spwoodcock , @NSUWAL123