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

Multiple decline reasons #78

enterprisey opened this Issue Feb 27, 2016 · 0 comments


None yet
1 participant

enterprisey commented Feb 27, 2016

The script should allow reviewers to decline a script for multiple reasons.

For example, if a draft reads like an advertisement and is poorly sourced, selecting both reasons should add a decline box that includes comments for both adv and v.

This is one of the most-requested, perhaps the most-requested, features for the script: see, for example, here and here.

In order for the feature to be added, the following tasks need to be accomplished:

  • Change the submission template (specifically, /declined) to support multiple reasons:
    • Investigate whether to use another param (e.g. {{{reason2}}}) or use Lua to parse a comma-separated list of reasons.
      • Resolve how to handle situations where both reasons need additional information (e.g. if both dup and exists are chosen, how are we going to store the duplicate article and the duplicate draft?)
      • Investigate feasability of a Lua version.
      • Investigate whether users would ever want to use three or more reasons at once.
    • Implement multiple decline reasons in /declined.
  • Update the script to support multiple reasons:
    • Add the capability in the user interface to select multiple reasons (presumably by changing our existing Chosen.js instance to multiple="true")
    • Allow the script to detect multiple selected reasons and update the decline template appropriately

@Technical-13 Technical-13 referenced this issue Feb 27, 2016


Todo list from June `14 BLD question #18

3 of 14 tasks complete

@enterprisey enterprisey self-assigned this Jun 22, 2017

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