[BUG] Lock-task error dialog shows a generic message instead of the actual reason

[jaroslav-kubicek]

When a user clicks "Map selected task" on a project they don't meet the requirements for, the API correctly refuses the lock — but the UI shows a generic dialog that doesn't say why:

It wasn't possible to lock this task for you...
Some error occurred when trying to lock this task. Check if your user matches the level, role and permissions required by this project.

The backend response actually contains the precise reason. For example, on POST /api/v2/projects/52246/tasks/actions/lock-for-mapping/2/ (production) I get:

{
  "Error": "Mapping not allowed because: MappingNotAllowed.USER_NOT_CORRECT_MAPPING_LEVEL",
  "SubCode": "MappingNotAllowed.USER_NOT_CORRECT_MAPPING_LEVEL"
}

So the information ("your mapper experience level is below what this project requires") is available, but never reaches the user.

Steps to reproduce

1. As a user whose mapping level is below the project's required level, open a project with a mapping-level requirement (e.g. #52246).
2. Select a task and click "Map selected task".
3. The generic "It wasn't possible to lock this task for you..." dialog appears.

Expected behavior

The dialog should state the concrete reason, e.g. "Your experience level is below the minimum level this project requires" — and similarly for the other rejection reasons (not a team member, etc.), for both mapping and validation locking.

[linear]

TECH-1229

[Tarekchehahde]

PR: #7294 — not runtime-tested locally (no yarn in CI env here).

[joshcord99]

Hi! I’m a junior studying computer science at California State University, Long Beach, and I earned a Full-Stack Web Development Certificate through the University of California, Irvine. I also have experience building software collaboratively. I’m interested in working on this issue. Is it still available? If so, I would be happy to take it on.