Staging Review 2

Collect, review feedback on bugs to help identify and prioritize issues this week

Issues list:

• Using feedback from staging testers and Thursday / Friday calls, decide Default group page, group submissions, and sidebar buttons action. Generate issues as needed.
• ⭐ ❓ Upon opening the top left nav bar, the vertical scroll bar should auto-scroll to the current group the user is in so they can see it upon opening. The problem is in groups with many subgroups (Olive Commission and Regen Digital have 50+ subgroups) the user feels lose if you start 'at the top' and can't see their current group. It's possible there are better options and this may require a discussion... there are potential real cases in which there will be many many nested groups (50 states, each state with 30 counties for example in the USDA Project 13 work)... in that case what is the experience of someone logged into the top level group? @desousab
• ⭐ Review pinned survey functionality... this may be removed in favor of pinning in the dropdown lists.
  • pinned surveys are really critical to the new UI, so I think having them in place will enable some important user journeys that aren't really possible today.
  • I asked for opinions about Pin versus Star. From our community it was split. Generally, Pin means "stick to top for everyone" which is what these do, along with make available offline. Star means "mark as important for me" and doesn't necessarily ensure the item is stuck to the top of a list. Thus, I think Pinning is more appropriate here, even though IMO it's a more 'old school' term.
  • @desousab: remove the pinned section in the group settings and add that function to the survey's three-dot-menu
• (greg) get/create design for empty lists
• (manuel) review loading performance of the following lists:
  • ❗ surveys (takes seconds to load for e.g. open team group, maybe due to new pipeline stages to sort by pinned and/or filtering out question sets) -> @gbathree can not reproduce slow loading on staging for OT group
  • question sets (takes seconds to load due to submission counts to be loaded, maybe these could be fetched async so the main request could deliver the list early)
  • @manuel-ch navigating through the app fetches memberships excessively. Causes:
    • calling getActiveGroupId of useGroups should not fetch memberships
    • reduce calls and/or use a vuex store (or tanstack) to reduce fetch. If caching is involved, make sure we understand and actively define the cache invalidation strategy.
  • Hint: also the staging infra could be a strong factor for fetch request to be slow - check this in parallel
• ⭐ Adding a subgroup does not update the list in the group selector in the top left with the new subgroup. @manuel-ch
• On mobile, you can swipe the navigation menu to the left or right to make it disappear. It is no longer possible to make it appear again. @desousab

Rolling wave planning of new features:

1. Drafts and responses: local/remote draft features, context actions @cryinbockritz
2. Default to the group menu pane when arriving to app.surveystack.io as a logged in user on mobile (as opposed to desktop where we default to "All My Groups")
3. make user profile and farmos profile modal dialogs (the two options in the top right user menu) @desousab
4. If user registers, take them to the one-time help page --> https://www.figma.com/design/vzbh76x1wyJEC3DyNev6N3/Our-Sci?node-id=2307%3A122&t=yv68tMVVJImSM8jt-1
5. questions set list: shows all questions sets instead of only the group's question sets. to be decided if we wanna stay with it as long as the explore feature is not available, so users may still access non-group qs @gbathree [ ] Drafts and responses: local/remote draft features, context actions @cryinbockritz
6. Add Intro modals for entity creation (Survey, QS, Script, Group) - see Figma for details. - Example here for Group Creation - https://www.figma.com/design/vzbh76x1wyJEC3DyNev6N3/Our-Sci?node-id=1688%3A556&t=SwHwZ8Sm3yMOVzgr @desousab
7. add response progress bar to draft (on top of active response draft view and on the list items of draft responses list and quick list
8. Explore Menu. This will allow users to more easily interact with entities outside their group, including finding QSs
9. Rights and Roles.
   • Explore menu won't really work right unless we have rights and roles in place
   • Pinned survey not showing up in the "All Surveys" list -> @gbathree the pinned survey does not show up in the group's surveys because its not a survey of that group. relates to the future permissioning rules. How to handle this in the meantime? -> For now, leave it until we get to updating permissioning rules @gbathree
   • Complete quick access buttons from Rights and Roles based on feedback
   • Check against rights and roles requirements - ensure all behavior is correct. --> #309
10. Add filters
11. Draft / submission leftovers of !419 (merged) :
    • ConfirmLeaveDialog does not display when leaving a draft on mobile due to the issue with the layout unnecessarily unmounting components without leaving the route.
    • For proxy and resubmission drafts, this means you aren't alerted that your draft won't be saved. That will lead to frustration.
    • For other drafts, it just means you won't be warned before leaving, and we'll miss the chance to sync the draft immediately upon leaving. It wills till be saved locally and synced eventually.
    • In the case of starting a new draft, and hitting the back button before making a change, you won't be prompted before leaving, and you won't have a way to return to that draft. You'll need to start the survey again.
    • The solution should be to not unmount the main content when a user looks at the menu on mobile
    • DraftsPage: do not show continue button on list row on mobile, or maybe at all, as it uses too much room.
    • Implement the context menu actions on the "My Responses" page
    • My Responses page just says "No Responses available" for unauthenticated users but should probably say something more informative, or maybe prevent them from getting there in the first place, or redirect to login?
12. test iframe mode
13. Add route guards similar to the permissions of the three-dot-menus @desousab
14. Update documentation as we go as things are released or solidified with review from staging.
15. From Week 2 discussion of Drafts, if we complete/deploy the first traunch of Drafts improvements.

• Ensure image references / s3 references in markdown and anything else we find as gaps are correctly stored as "Resources" in the Survey object. That way they will be correctly cached with all other resources.
• There should be a clear loading bar on opening the application showing that any items (Drafts, pinned Surveys, Resources, etc.) that should be available offline are being loaded.
  • (greg, manuel) create UI for this before implementing
• Creating offline mode which improves the user experience
  • (greg) scope best use cases regarding this, good Miro
  • create the best long-term implementation of offline mode identification (offline flags, etc.) - we'll use this a lot.
    • hide / grey parts of the application, etc. etc.