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

Marking a Response as the Best Response #16

Closed
Procos12 opened this issue Sep 12, 2024 · 2 comments
Closed

Marking a Response as the Best Response #16

Procos12 opened this issue Sep 12, 2024 · 2 comments
Assignees
Milestone

Comments

@Procos12
Copy link

Procos12 commented Sep 12, 2024

In this issue, we will allow anyone to mark a response to a question as the best response. This opens the door for us to limit this ability to only instructors later.

Estimated Effort:
Finding the right place to add the component in the code may be troublesome, however I do not see implementing this feature as an something difficult. I expect it to take about a week or less.
Estimated time: 5 days

Dependencies:
None

Initial assignments for team members:
Assigned to Abdulwahab Al-Rumaihi

Milestones to indicate which sprint the issue should be completed in:
This should be complete by the end of sprint 1

Acceptance criteria:
Anyone can have the ability to mark a response as the best response. We will test it on a running version of nodebb to see if this is the case. Afterwards the best response should clearly be indicated within a post.
In another issue, we will limit the ability of selecting the best response only to the instructor.

@Procos12 Procos12 self-assigned this Sep 12, 2024
@Procos12 Procos12 changed the title Marking a Response as the Best Response 2: Marking a Response as the Best Response Sep 12, 2024
@Procos12 Procos12 changed the title 2: Marking a Response as the Best Response Marking a Response as the Best Response Sep 12, 2024
@hibaabdullahhamad hibaabdullahhamad added this to the Sprint 1 milestone Sep 15, 2024
@Procos12
Copy link
Author

Issue was too big, have to refactor into multiple other issues, will be commented on later

@Procos12
Copy link
Author

Divided into #39, #40, #41

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

No branches or pull requests

2 participants