Meeting Minutes (Meeting with Team)

Date: 2026-03-03
Time: 20:30 - 21:50
Location/Platform: Online(Google Meet)
Facilitator: Aditya

Attendance

  • Attendees: Aditya, Salaar Prajin, Smriti
  • *attendance doesnt matter because this was an unscheduled team meeting(right after client meeting)

Discussion & Agenda

  • only discussed about bugs, remaining US to complete
  • discussed other clarifications required regarding sprint 3 deliverables

Decisions Made/Next Steps

Clarification Required:

clarify with client: remove all web stuff(code, checking web build in CI CD), only app code - wait for client/social worker confirmation - let that be, make admin web compatible in later sprints

TASKS ASSIGNED/DISCUSSED TODO:

Aditya:

  • ask for retention input date in create client page
    • both storing, deleting recordings individually set by administrator(policy set from the app)

  • add feature in manage cases:

    • filter by client, date
    • if client is closed, dont show any cases of them by default(show using a seperate button to see closed clients)
      • admin can reopen the case as well

  • npm depretiated packages fix

  • generate ssh keys for client vm, send to team members
  • API SECURITY: make edge functions(to protect api security) for the 2 AZURE things
  • upload .apk as an artifact to github CI CD(maybe using eas-cli):
  • make push flag: ensure supabase pull, test-fix, and other stuff to ensure running/fixing before commiting
  • make diff for file diff excluding files not req
  • main dashboard topbar is not consistent with other screens
  • admin topbars are not consistent across the 5 tabs
  • logout not present on one of the screens - make a common component to keep consistency
  • remove profile picture from recent cases, cases listed under cases
  • Migrate from it() to test() for jest tests
  • optional(if time persists):
    • make more tests for fulfulling jest coverage report
    • make a workflow for handling kanban board(inprogress, ready for review)
    • Add OpenAI api key to supabase for supabase AI features(azure foundry model vs legacy openai api format)
    • Jest tests visualization of the app(like java) if jest supports that
    • Check alternatives better than Resend for free tier and/or self host SMTP server(maybe opensource from github) in later sprints

CODE CLEANUP(Aditya):

  • jsdom comments(and look into report/coverage generation)
  • remove console.log() if its a security hazard(exposing user ids)
  • remove console.debug stuff if it was just for testing
  • move stuff from scripts/ to src/
    • duplicate files under scripts/ and src/ like authProviderFactory.ts
    • cleanup scripts/ folder
  • refactor rtm(testing matrix) code
    • include all tests in testing matrix rtm, even if pass/fail, exists/doesnt exist
    • integrate testing matrix into makefile, package.json, npm test
    • add verify AC coverage to CI CD
      • not as a pass/failure, just display
      • or maybe add to npm test(jest)
  • update depretiated packages, errors, old SDKs
  • put constants in constants, then remove hardcoded from files, and reference it instead
  • remove identifying “user story” comments(example "US 11.04 ...")

Prajin:

  • recording:
    • before: screen change deletes recording
    • after: fix it(will look into it)
  • update low fidelity workflow(wireframe)

Salaar:

  • make 4 big cards on practioner home clickable
  • active filter for cases page is not working
  • delete the “plus” icon on cases page(prac acct)
  • fix stats on profile page
  • recent cases to limit showing recent 3 cases acc to last updated
  • address RLS issues on supabase

Smriti:

  • do the UML fixes off of sprint 1(check 25 feb meeting minutes)

Mustafa:

  • practioner uploads forms not admin
  • display pdf in the app
    • dont stress much about pdf formatting, focus on data accurately stored

Pragya:

  • fix login invalid credentials to instead display error popup
  • password:
    • enforce strong password standard
      • character length, capital letter, number, special characters, neither name nor email(not even its subset) to be part of password
  • mark sprint4, sprint5 US

Other bugs to fix(needs to be done, but no one assigned yet):

  • fix scrolling bug for the last input box
  • look into acessibility
  • edit client:
    • doesnt allow country code to be changed
    • check error handling for email, make it red box
    • NOTE: do this in the common component, not edit client
  • save location(when session created)
    • good to have: small google maps minimap OR maybe openstreetmaps(aditya has experience with openstreetmap)
  • do live sync so no logout login(anytime, not necessarily by sprint 3)
    • logout user if invalid JWT/token
    • "remember me" functionality on login page

Docs Update:

  • add/update the new branching strategy
  • assign issues to future milestones, assignees
  • update all 4 docs properly thoroughly
    • verify those docs with github

Future Sprints TODO:

  • timestamps for notes linked to the timing of the recording
  • notifications(maybe)
  • auto deletion(delete all related, and all child objects recursively)
  • CLARIFY WITH CLIENT FIRST:
    • Options:
    • (1) cases cannot be accessed offline, so download all of them upon login
    • (2) put a toggle on all cases for availiable offline(yes/no) and download them accordingly

Confirm with TA:

  1. consider accessibility in sprint3

    Accessibility is considered and described in the docs
    (e.g. colors pass contrast check, see https://accessibilityaid.com/free-tools/colour-contrast-checker)

  2. using expo go, apk required or not?, testflight $99/year apple developer account subscription required

    Project is deployed to a non-local (production-like) environment,
    and acceptance tests are executed against the deployed system (not a local development instance)

  3. confirm if we did labels properly done or not

References/Attachments