learningequality / learningequality/kolibri

Can't review past responses to a survey after pressing "Submit again"

Open
#13,633 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

TODO: needs clarification TODO: needs decisions
Dominant language
Python
Stars
1.1k
Forks
972
Avg merge
7d 16h
Merged PRs (30d)
33

Description

This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Observed behaviour

This one looks like a blocker to me:

  1. Open survey in a lesson, write responses and submit.
  2. View the responses in the survey report.
  3. Click Submit again button but do not input any responses on this second attempt.
  4. Click the Back button and you will be back to list of resources in the lesson.
  5. Click to open the survey resource and it will open in that un-submitted attempt, and there's no way to view the report of the first attempt until the submit.

https://github.com/user-attachments/assets/ac0b19e7-bbc3-4bf5-b6df-8e82866379f7

Originally posted by @radinamatic in #13599

It's not entirely clear that this is a blocker for anyone in the way that surveys are currently being used. Let's hold off on deciding on a solution here until we see similar requests from usage to understand the desired use case here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the survey flow described: submit responses, open the report, choose Submit again without answering, then navigate back and reopen the survey. No file, test, or entry point is named; first identify the survey resource and report implementation, confirm the desired behavior with maintainers, and define done as preserving access to the earlier report after the empty second attempt.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.