maproulette / maproulette/maproulette-frontend

Idea: Survey/feedback for challenge owner at the end of a challenge

Open
#1,592 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
167
Forks
39
Avg merge
16h 34m
Merged PRs (30d)
11

Description

At the end of a challenge, in addition to the "congratulations" pop-up, have a way for a user to provide feedback on the challenge and allow them to peruse similar tasks based on challenge or challenges made by the same challenge creator.

  • Have a simple click (Up Down/Thumbs Down) to allow users to express their feeling to the task in addition to the normal close button. Nothing super in depth (as the more complex it is mad, the faster the user will likely ignore the feedback option), just one or two buttons.
    - When a user does this, have an optional feed back box that will allow a user to give a reason why they liked or disliked a challenge. Both the rating and the feedback will be sent to the challenge creator's inbox for review to hopefully improve projects going forward.

  • If a user did like the challenge, perhaps have a way to have the user directed towards other tasks of a similar name/feature to allow them to continue or even allow for the user to find other projects made by the same task owner (challenges marked as public only)

This also could be used midway through a challenge as well to gauge user feedback toward the project, but I would avoid having it be overly intrusive, as it can lead to a negative experience with the site.

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

No files, tests, or entry points are named. Start by locating the challenge-completion popup and the challenge creator inbox, then clarify the feedback, similar-task, and public-creator-task requirements before implementation. Done would include an agreed interaction design and tests for the selected feedback and discovery flows.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.