Open plschmitz opened 1 year ago
We could use something like https://github.com/SortableJS/Sortable and when they drop, we could reset the priorities in the UI so they see what is happening. They could revert/cancel, or save to update the priorities in the assessment (i.e., DB).
Adding Lauren to review any spec we come up with
Users should be able to see the full list of items they priorities, and reorder them in some straight-forward manner. This could include a widget to push an item up or down in the list (which may require some intelligence about resetting the priority values of a list), or it could just keep a local order and then renumber them upon a save function.
Users may choose to do this for all questions together, or might choose to separate the task by facing (since different teams may work on different areas, and this global priorities might make little sense for their org). There would be a UI choice to view-by-facing, or view-all-together. If they view by facing, the renumbering would be local to the facing, and so switching to view-all-together would sort all the 1's, then the 2's, etc. Switching from view-all-together to view-by-facing would preserve ordering and just show individual lists. This would have to be documented well.