List view

• 0 - Sprint priorities August 2025

  Top items for the next development sprint, timing TBD.

  No due date

  •12/14 issues closed
  85% complete2 open12 closed

• 1 - Improve "Assessments"

  This milestone includes issues to improve the functionality of the Assessments landing page and sankey diagrams

  No due date

  •7/20 issues closed
  35% complete13 open7 closed

• 1 - Training Material

  Materials (videos, FAQs) and webpages that support user interactions with the Benefit Tool

  No due date

  •2/9 issues closed
  22% complete7 open2 closed

• 2 - Implement user management

  1. Surveys can be assigned to respondents 2. Private surveys can only be viewed by the assigned respondents and admin 3. Non-private surveys can only be edited by the assigned respondents and admin 4. Surveys assigned to a respondent are highlighted on the home page

  No due date

  •0/6 issues closed
  0% complete6 open0 closed

• 2 - Improve "Object Library"

  The Object Library is a registry of response objects that admins are able to pre-populate, and respondents can add to or select from while creating a response. These objects don't include ratings, just the information about the object. They are listed here: https://usaon.org/apps/benefit-tool/objects This milestone includes issues to improve how objects are created, modified, listed, deleted, and viewed.

  No due date

  •3/15 issues closed
  20% complete12 open3 closed

• 2 - Robust data management

  * Support data export to admins * Support data export to end-users (JSON?)

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• 3 - Accessibility

  https://www.worthwhileconsulting.com/read-watch-listen/what-counts-as-viable-for-a-minimally-viable-product

  No due date

  •0/2 issues closed
  0% complete2 open0 closed

• 4 - Sustainability

  There's no urgency on this, but we want to make sure it's done before our money runs out. Play it by ear, make sure we leave ourselves in a good spot. A lot of sustainability tasks can be done as-we-go, because we'll be touching the relevant component for other reasons. We shouldn't dogmatically wait to address sustainability :)

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• 4- Improve user messaging for errors and successes

  When something in the db is successfully changed, we should display something. When something goes wrong, we should display clear messaging and give the user a way to recover. In QA, currently a `500 internal server error` is displayed.

  No due date

  •0/2 issues closed
  0% complete2 open0 closed

• 9 - Issues for Tyler to explore

  See what you can do with these and if there are any that are resolvable

  No due date

  •0/3 issues closed
  0% complete3 open0 closed

• Other ideas and reference material

  Parking lot for long-term items

  No due date

  •1/5 issues closed
  20% complete4 open1 closed

• Unsorted issues

  Noted during pause in development, will be prioritized and sorted once dev resumes

  No due date

  •0/1 issues closed
  0% complete1 open0 closed