Frontend task_id is out of sync with db task_id

[spwoodcock]

Describe the bug

When updating task 9, the popup shows I am looking at task 8:

• The backend handling of task_id based on project_task_index appears to be correct.
• I think the issue is because the task index starts at 1 to be more user friendly.
• The frontend references the index of the tasks, which will start from 0:

Expected behavior

The task id on the task popup should match the actual task index id from the backend.

[NSUWAL123]

@spwoodcock, I think it's working fine.

Here I have tested with task id of 1260 with task index of 4.

/Project API response:

Post new status and it's response:

Task History API fetch:

@spwoodcock and @manjitapandey also, could you please confirm from your side too.

And Sam, your action text seems to look different from the current action text: "action_text": "Status changed from MAPPED to LOCKED_FOR_VALIDATION by: localadmin",

[spwoodcock]

Thanks for such detail!

I can check this on Monday 👍

I'm testing on the mapper frontend branch, so perhaps it's just an issue on my end. I tweaked the action text a bit on the branch.

@spwoodcock

[manjitapandey]

@spwoodcock waiting for your confirmation.

[spwoodcock]

This is actually fine 👍

Perhaps a bug introduced on my local mapper frontend branch, or just a some confusion somewhere - closing!