Editors should be opened for tasking manager repo instead of openstreetmap editor

[manjitapandey]

Describe the bug
When user opens the validated task on editor view, it is redirected to openstreetmap link instead of tasking manager link.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'tasks page' and select any validated task
2. Click on 'open editor and select id editor'
3. See the URL opened to openstreetmap ID editor instead on TM Id editor
4. See error

Expected behavior
Users should be redirected to Tasking manager editor instead of Openstreetmap editor.
Screenshots

Additional context
Also the task boundary is removed once user refresh the page.

[manjitapandey]

When attempting to open HOT’s integrated iD editor for a feature already marked as finished, a logic conflict arises if the user has another task locked, since multiple tasks cannot be opened simultaneously.
cc: @royallsilwallz

[Ashik-AD]

Hey, just to give some context on the request to open successful or validated tasks in the integrated editor instead of OSM:

Right now, the way things are set up, a task has to be locked in order to be opened in our editor. That’s by design, it helps us prevent conflicts and makes sure only one person is working on something at a time. But once a task is completed or validated, we intentionally skip locking, since those tasks aren’t meant to be edited anymore. They’re essentially final.

That’s where the limitation comes in, since the integrated editor only works with locked tasks, trying to open a completed task there doesn’t fit into the current logic without changing how locking works.

We’ve thought about a few ways around this:

• One option is to allow locking for completed tasks, but that could get a bit confusing, it might suggest the task is editable again.
• Another is to continue using the external editor for those finalized tasks, since it's already separate from the lock/edit flow.
• Or, potentially, we could look into adding a read-only mode to the integrated editor, but that would need extra dev time and design effort.

Happy to talk through what makes most sense here depending on how important this is for users. Just wanted to surface the constraint so we’re all on the same page.

cc: @manjitapandey @royallsilwallz

[ramyaragupathy]

Thanks for digging into this @Ashik-AD 🙏

Right now, the way things are set up, a task has to be locked in order to be opened in our editor. That’s by design, it helps us prevent conflicts and makes sure only one person is working on something at a time. But once a task is completed or validated, we intentionally skip locking, since those tasks aren’t meant to be edited anymore. They’re essentially final.

That makes it clear. We should stick to the same behaviour.