Auto Implementing Change Requests

Overview

Currently the way we manage / implement change requests is we request a change then manually implement the changes once its been approved. instead we want to give the user the ability to propose all the changes to a wbs element first and then submit a change request that once approved will automatically propogate the proposed changes to the actual wbs element.

Stakeholders

Product Stakeholder: Peyton McKee
Software Stakeholder: Sean Walker
Reference Users: David Murawski

User Story

As the creator of a change request, I want to be able to create all the changes i want to make to a wbs element before submitting a change request, so that when its approved I dont have to go in and make the changes, they will just be automatically implemented upon approval.

Success Metrics

People will pretty much only use this im pretty sure other than for delay requests

Rollout Plan

All at once

Out of Scope

n/a

Background / Context

See description

Acceptance Criteria & Mock-ups

• Edit Schema
• Edit Endponits
• Edit Frontend Types and Displays
• Compilation and passing tests

Tickets

• #1893
• #1894
• #1896
• #1897
• #1898
• #1899
• #1900
• #1901
• #1902
• #1903
• #1904
• #1905
• #1906
• #2277

Start by reviewing the completed tickets listed in the issue, especially #1893–#1906 and #2277, to understand the existing change-request work. Then trace the schema, endpoints, and frontend types and displays named in the acceptance criteria. Done means the proposed WBS changes propagate after approval, compilation succeeds, and tests pass.