Skip to content

Conversation

@yyassi-heartex
Copy link
Contributor

This pull request introduces an important fix to the task navigation logic in the data manager queue of the labeling workflow. The change ensures that when a user clicks "next" in the label stream, they are not repeatedly assigned the same locked task, allowing for smooth progression through tasks.

Task navigation improvements:

  • Updated the logic in get_next_task (in label_studio/projects/functions/next_task.py) to exclude the currently locked task when using the data manager queue, preventing users from getting stuck on the same task when navigating forward.

@netlify
Copy link

netlify bot commented Dec 10, 2025

Deploy Preview for label-studio-docs-new-theme canceled.

Name Link
🔨 Latest commit fc0da22
🔍 Latest deploy log https://app.netlify.com/projects/label-studio-docs-new-theme/deploys/6939b9fcc37b0c0008602688

@netlify
Copy link

netlify bot commented Dec 10, 2025

Deploy Preview for label-studio-storybook canceled.

Name Link
🔨 Latest commit fc0da22
🔍 Latest deploy log https://app.netlify.com/projects/label-studio-storybook/deploys/6939b9fc8397ab0008d54351

@netlify
Copy link

netlify bot commented Dec 10, 2025

Deploy Preview for heartex-docs canceled.

Name Link
🔨 Latest commit fc0da22
🔍 Latest deploy log https://app.netlify.com/projects/heartex-docs/deploys/6939b9fc4deb490008f6732c

@yyassi-heartex yyassi-heartex requested review from a team December 10, 2025 18:20
@github-actions github-actions bot added the fix label Dec 10, 2025
@netlify
Copy link

netlify bot commented Dec 10, 2025

Deploy Preview for label-studio-playground canceled.

Name Link
🔨 Latest commit fc0da22
🔍 Latest deploy log https://app.netlify.com/projects/label-studio-playground/deploys/6939b9fc93e2020008f55f76

# 1. not_solved_tasks excludes completed tasks but not locked tasks
# 2. .first() would keep returning the locked task
# 3. The user would be stuck on the same task unable to progress
locked_task = Task.get_locked_by(user, tasks=not_solved_tasks)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a fix for the tests but I wonder how this will affect production logic

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

valid concern - i'd much rather a frontend solution - but this seems to be the only consistent solution

@yyassi-heartex
Copy link
Contributor Author

closing this PR - addressing issue by cleaning up the test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants