Reviewer Selection & Fee Conditional Logic

[acshields]

Update 1: Q/A Structure

• Question field label: "Review Type"
• Answer format: Checkboxes -Community Review -Internal Review -Automated Review

Update 2: Conditional Logic Scenarios

Scenario 1 Pre-Conditions:

• Format = Task Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Internal"
• The default answer can be modified by the user by: -Unselecting the default and selecting an alternate -Selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is displayed in the Advanced Settings "Prizes" section
• The "Reviewer Fee" has the default value of X
• The default value can be modified by the user

Scenario 2 Pre-Conditions:

• Format = F2F Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Internal"
• The default answer can be modified by the user by: -Unselecting the default and selecting an alternate -Selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is displayed in the Advanced Settings "Prizes" section
• The "Reviewer Fee" has the default value of X
• The default value can be modified by the user

Scenario 3 Pre-Conditions:

• Type = Design Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Internal"
• The default answer can be modified by the user by selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is displayed in the Advanced Settings "Prizes" section
• The "Reviewer Fee" has the default value of X
• The default value can be modified by the user

Scenario 4 Pre-Conditions:

• Type = Data Science
• Tags = Does not include "Marathon Match" Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Community"
• The default answer can be modified by the user by: -Unselecting the default and selecting an alternate -Selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is displayed in the Advanced Settings "Prizes" section
• The "Reviewer Fee" has the default value of X
• The default value can be modified by the user

Scenario 5 Pre-Conditions:

• Type = Data Science
• Tags = Includes "Marathon Match" Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Automated"
• The default answer can be modified by the user by: -Unselecting the default and selecting an alternate -Selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is hidden by default if "Automated" is the only reviewer type selected
• If the user selects additional reviewer types, then the "Reviewer Field" should be displayed with the defaulted and editable value of X.

Scenario 6 Pre-Conditions:

• Type = Development, or Quality Assurance
• Format = Challenge Reviewer Selection:
• The "Reviewer" field is displayed in the Advanced Settings "Participants" section
• The "Reviewer" field has the default answer of "Community"
• The default answer can be modified by the user by: -Unselecting the default and selecting an alternate -Selecting additional answers Reviewer Fee:
• The "Reviewer Fee" field is displayed in the Advanced Settings "Prizes" section
• The "Reviewer Fee" has the default value of X
• The default value can be modified by the user

[vikasrohit]

If the track selected is Data Science, the type is Challenge, and it is indicated that it will be a Marathon Match, then the default answer option selected should be: "Automated Review"

@acshields does that mean that user can select any of other review type for Marathon Match?

[acshields]

@vikasrohit - Yes, I spoke with Lazy on this yesterday. For Marathon Matches, Automated Review is the default. However, in some cases, delivery teams also choose to incorporate a Community Reviewer or Internal Reviewer into the process as well.

So, essentially, for all of our tracks, there will be a default answer. However, the user could choose to add in additional review types in Advanced Settings if desired.

[vikasrohit]

Thanks @acshields. I am moving it back to November project because as we discussed we have to start on all of the design updates (at least for the creation form) simultaneously. This issue is tightly coupled with https://github.com/topcoder-platform/work-manager/issues/736

[maxceem]

1. What value should we save to the API into legacy.reviewType for Automated Review, automated?

[vikasrohit]

@rootelement help needed. :)

[cwdcwd]

call to https://api.topcoder.com/v5/reviewTypes?name=Automated%20Testing%20Review to get the Id of the review type for v5.

[rootelement]

@maxceem you don't need the ID, you should just be able to use the name. It looks in the legacy-challenge-processor like we're setting the default to INTERNAL, so the name should be fine. We'll have to test it in dev.