Adding Approval Process for Hack for LA Project Updates

[AmandaGlover-PM]

Dependency

Issue is too long and needs to be re-written once specs are collected.

Overview

When reviewing how to optimize the project pages for VRMS for improvements, Bonnie requested an added feature to have an approval process built into VRMS so PMs can request changes to their project webpages. This would incorporate a review and approval process and kick the request to a developer once fully approved.

Current State:
The GitHub page is an issues page for the website so people can propose relevant changes to the website – Bonnie reviews this and once she’s convinced the change makes sense she reviews/approves and turns it over to developers to update.

Why? This process lives in Github now and requires additional work for Bonnie that can be streamlined. She goes back and forth to approve the changes and then ultimately once approved she passes the work to a developer. The approval process can be automated and ultimately it sounds like once approved, it can get kicked over to a developer versus Bonnie having to facilitate next steps. This means we are now leveraging the VRMS database and the Github process goes away, thus adding more immediate value and functionality to VRMS, providing more reasons for PMs to actively use VRMS.

What Does a Completed Version Look Like?
-We have the ability to approve and deny changes in order to edit their data on the project page in VRMS
-We’ve mapped out a review process & have designed what the screens look like
-We have solutions for partial approvals or non-approvals
-There is a process that kicks the request back to the originator for review when not approved
-Once approved can this go to a developer directly for implementation

Some Acceptance Criteria:
Wants VRMS to mimic the same process done on Github – the same main things need to happen:
-Project leads need to suggest changes to their pages
-Review process needs to be fully functional
-Communication means to go through the approval process
-The approval process automatically changes the database

We are creating screens with the same features from the existing process to migrate that process to VRMS. Once those features are rolled out – all PMs will be directed to VRMS to request these updates and the Github process shuts down. Changes will happen moving forward in the VRMS database.

Action Items

Need to map out:
-What is the review process like
-What do the screens look like
-What is the approval process is
-What happens if you only approve 3 out of 5 things for example; can we selectively approve?
-What happens if something is not approved?
-Does this go back to the originator? How? This needs to happen automatically in the system itself

Resources/Instructions

TBD

[juliagab56]

Is this still a requested feature?