Give New Feedback/Existing feedback card redesign
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
# TL;DR
The Give New Feedback/Existing Feedback card on the researcher's Individual Response view could be redesigned for an easier user experience.
# Narrative
This card can both add new feedback and update existing feedback. We're unsure if this card meets its normal use case, and this card may already do what it needs to do. Nevertheless, feedback from the researcher community could clear up confusion on this matter.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Give New Feedback/Existing Feedback card on the researcher's Individual Response view and review how it handles adding versus updating feedback. Seek researcher-community feedback to determine whether confusion exists and agree on the redesign scope. Done means an agreed user-experience change is specified; this issue does not name files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100