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

Restricting the option to "Mark a response as the best response" To instructors only #17

Open
Procos12 opened this issue Sep 12, 2024 · 0 comments · May be fixed by #62
Open

Restricting the option to "Mark a response as the best response" To instructors only #17

Procos12 opened this issue Sep 12, 2024 · 0 comments · May be fixed by #62
Assignees
Milestone

Comments

@Procos12
Copy link

Procos12 commented Sep 12, 2024

#16 Allowed all users to mark a response as the best response. Finishing up the requirement in the second user story, we should limit this feature only to instructors.

Estimated Effort:
Around 1 week and a half to two weeks. Not sure if limiting the option to instructors only would be medium-effort or a lot of effort.

Dependencies:
#16

Initial assignments for team members:
Abdulwahab Al-Rumaihi

Milestones to indicate which sprint the issue should be completed in:
Should be completed by sprint 2

Acceptance criteria:
The functionality will be tested on a live version of nodeBB by the team. To accept this, we will experiment and see if all instructors have access to this feature and that no students are able to mark a response as the best response.

@Procos12 Procos12 self-assigned this Sep 12, 2024
@Procos12 Procos12 changed the title 2: Restricting the option to "Mark a response as the best response" To instructors only Restricting the option to "Mark a response as the best response" To instructors only Sep 12, 2024
@njouud njouud added this to the Sprint 1 milestone Sep 12, 2024
@Procos12 Procos12 modified the milestones: Sprint 1, Sprint 2 Sep 17, 2024
@Procos12 Procos12 linked a pull request Oct 9, 2024 that will close this issue
@Procos12 Procos12 linked a pull request Oct 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants