List view
- No due date•0/1 issues closed
- No due date•2/2 issues closed
Things that we don't have to do, but if we run out of other issues to do and they have been approved, someone can work on it.
No due date•35/47 issues closedRefactoring that will improve development time, site loading, etc.
No due date•9/22 issues closedAll onboarding occurs on VRMS with the exception of Bonnie's live Hack for LA intro talk. (includes: Github, CoP Google Drives, Calendar & Slack invites, and code of conduct agreement).
No due dateRosters should be available to PMs and users with specific data hidden according to user access levels, replacing the current methodology of storing roster data in spreadsheets on each project's Google Drive.
No due date•1/1 issues closedIf VRMS data collection secure, could turn this form into VRMS, and write data to Tables, allowing validation on form fields, which would reduce the manual review and rework for people who make mistakes.
No due dateProject orchestration of VRMS: - Agendas - Roadmaps - Updates to HfLA website, etc.
No due date•39/49 issues closedLegal compliance issues.
No due date•0/1 issues closedCreate a new user account on VRMS
No due date•0/1 issues closedFeatures which aid the adding of people to project resources by PMs.
No due date•0/1 issues closedTransitioning back end to People Depot, including identifying custom SQL queries, requirements for basic APIs, and rewriting all of the API calls that are currently using People Depot's MongoDB
No due date•1/2 issues closed- No due date•10/20 issues closed
Identity access management (IAM). This requires People Depot back end.
No due date•16/20 issues closedAny issue that addresses VRMS team member onboarding, processes, reviewing PRs, handoffs between practice areas, etc.
No due date•13/19 issues closedAnything users write us about what is not working for them with VRMS
No due date•4/5 issues closedPMs submit request for changes to project profile, Org rep reviews and approves/rejects the changes with notes.
No due date•21/29 issues closedEverything that is an existing feature that is not divided up into sub-milestones below.
No due date•72/94 issues closedProject data API in use by website team.
No due date•11/12 issues closedHow the site is architected, documentation for site architecture, etc.
No due date•75/89 issues closedGoogle Analytics data - what's happening on the site, usage of the application by internal users (e.g., how many PMs logged in to make changes over the past year to meeting times / project data, what project made the most amount of changes, product adoption etc.) Allows us to see the impact of new feature releases.
No due date•3/3 issues closedReports for the Org - model usage & behavior data from VRMS (e.g., prospective member drop offs, length of time, average project team member length per project, MAU etc.)
No due date•1/2 issues closedCode of conduct passphrase validation and ability to check in to onboarding meetings.
No due date•9/11 issues closedDashboards for user access levels (prospective member, team member, project and CoP leads, admins).
No due date•10/11 issues closedAny user logging in to VRMS.
No due date•19/25 issues closed