Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow super admin or project creator to unlock task or revert to ready for mapping #2181

Closed
manjitapandey opened this issue Feb 12, 2025 · 2 comments
Assignees
Labels
effort:low Likely a few hours enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority testing:ready Ready for testing

Comments

@manjitapandey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
In field mapping exercise there is maximum chances that user can lock task or mark task as mapped without mapping completely or leave the task mapping midway. In such cases, there is no workflow to undo these actions causing users not being able to map new features or provide false information to management team.

Describe the solution you'd like
Provide the access to super admin or project creator to unlock the tasks locked by mapper or reset the mapped task to ready for mapping state.

Describe alternatives you've considered
Alternatively, for now we can add map new feature button on mapper frontend irrespective of task but this will also cause problem in validation workflow later and its good that features and submissions are linked to task ID.

Additional context
Add any other context or screenshots about the feature request here.

@manjitapandey manjitapandey added enhancement New feature or request priority:high Should be addressed as a priority backend Related to backend code labels Feb 12, 2025
@spwoodcock
Copy link
Member

We have the code in place to already do this, in a PR that unlocks based on a cron.

The simple thing to do would be:

  • Endpoint with project admin permissions
  • Use the same logic as the cron for unlocking tasks (DRY code)

@manjitapandey manjitapandey added the testing:ready Ready for testing label Feb 19, 2025
@spwoodcock spwoodcock added frontend Related to frontend code effort:low Likely a few hours and removed backend Related to backend code testing:ready Ready for testing labels Feb 20, 2025
@spwoodcock spwoodcock assigned NSUWAL123 and unassigned Anuj-Gupta4 Feb 20, 2025
@spwoodcock spwoodcock added this to the (2025.x.x) Next Release milestone Feb 20, 2025
@spwoodcock
Copy link
Member

Actually, I realised this has a frontend part I think:

  • Currently, if a user has locked a task, another user can't unlock it. This is a restriction imposed by the frontend.
  • If the user if a project manager or greater, we want to allow them to unlock the task by calling the API.
  • Related to Frontend user roles integration #2207, where we want to use const isProjectManager = useIsProjectManager();, the we we have conditional logic to allow the user to trigger an unlock of the task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort:low Likely a few hours enhancement New feature or request frontend Related to frontend code priority:high Should be addressed as a priority testing:ready Ready for testing
Projects
Development

No branches or pull requests

4 participants