You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Old backend had a system for setting a "high priority" property on maps. I didn't port it originally as frankly I didn't fully understand what it was (the implementation was quite weird). But we can definitely make it work, in fact it'll integrate a lot better with the new MapSubmission table. Doing this myself, given a quick spec here:
Add a boolean field for called highPriority (can't think of a reason to have more than two priority levels) on the MapSubmission table/model, default false.
Allow reviewer/mods/admins to filter by priority (undefined in query means no filtering)
Get rid of the two separate queue components on the admin map, just show it on a column in the list and have a dropdown to filter by on/off/none
Allow REVIEWERS to fast-track a map straight to FINAL_APPROVAL, skipping public testing. Allow admins/mods to approve a high priority map at any point after private testing (including if they're setting a map to high priority in that request).
The text was updated successfully, but these errors were encountered:
Old backend had a system for setting a "high priority" property on maps. I didn't port it originally as frankly I didn't fully understand what it was (the implementation was quite weird). But we can definitely make it work, in fact it'll integrate a lot better with the new
MapSubmission
table. Doing this myself, given a quick spec here:highPriority
(can't think of a reason to have more than two priority levels) on theMapSubmission
table/model, default false.The text was updated successfully, but these errors were encountered: