Change Requests | Approval Workflow and Notes

[sethmcknight]

Implement the below Steps for Change Requests.

At each Step provide a text box for the user to leave notes with their selection.

Store the notes and display the notes along with the step changes on the Change Request.

Steps for Change Requests

Step 1 | Discussing Change

Approvers

• Project Manager
• Regional Director
• Field Operations Director

  Next Step Options

• Approve (Approved)
• Submit for Regional Director Approval (Pending Regional Director Approval)
• Submit for Financial Endorsement (Pending Financial Endorsement)
• Submit for Consultant Endorsement (Pending Consultant Endorsement)
• Will Not Change Plan (Did Not Change)

  Notifications

• Team

  Step 2 | Pending Financial Endorsement

  Approvers

• Financial Analyst
• Lead Financial Analyst
• Controller

  Next Step Options

• Endorse Change Request (Finalizing Change Request)
• Do Not Endorse Change Request (Finalizing Change Request)

  Notifications

• Team

  Step 3 | Pending Consultant Endorsement

  Approvers

• Consultant
• Consultant Manager
• Project Manager
• Regional Director
• Field Operations Director

  Next Step Options

• Endorse Change Request (Finalizing Change Request)
• Do Not Endorse Change Request (Finalizing Change Request)

  Notifications

• Team

  Step 4 | Finalizing Change Request

  Approvers

• Project Manager
• Regional Director
• Field Operations Director

  Next Step Options

• Approve (Approved)
• Submit for Regional Director Approval (Pending Regional Director Approval)
• Submit for Financial Endorsement (Pending Financial Endorsement)
• Submit for Consultant Endorsement (Pending Consultant Endorsement)
• Will Not Change Plan (Did Not Change)

  Notifications

• Team

  Step 5 | Pending Regional Director Approval

  Approvers

• Regional Director
• Field Operations Director

  Next Step Options

• Approve (Approved)
• Approve for Finance Confirmation (Pending Finance Confirmation)
• Reject (Rejected)

  Notifications

• Team

  Step 6 | Pending Field Operations Director Approval

  Approvers

• Field Operations Director

  Next Step Options

• Approve (Approved)
• Approve for Finance Confirmation (Pending Finance Confirmation)
• Reject (Rejected)

  Notifications

• Team

  Step 7 | Pending Finance Confirmation

  Approvers

• Field Operations Director

  Next Step Options

• Confirm (Approved)
• Reject (Rejected)

  Notifications

• Team

┆Issue is synchronized with this Monday item by Unito

[sethmcknight]

An example of how we might display the Notes and Step Changes:

[CarsonF]

Ok so one step at a time. I think we need this new schema:

type Mutation {
  transitionProject(input: ProjectTransitionInput!): ProjectTransitionOutput!
}
input ProjectTransitionInput {
  id: ID!
  changeset: ID
  step: ProjectStep!
  comment: String
}
type ProjectTransitionOutput {
  project: Project!
}

type SecuredProjectStep {
  history: [ProjectStepChange!]!
}
type ProjectStepChange {
  step: ProjectStep!
  by: User!
  comment: String
}

• Does transitionProject() or changeProjectStep() make more sense?
• These should fully work with changesets
• Maybe we deprecate updateProject.step for this new mutation as well?

Once this is done we can talk about integrating changeset status and project step workflows.

[ParkeBrown]

@sethmcknight we'll need to break this down

[sethmcknight]

Moved this to #2273

Ok so one step at a time. I think we need this new schema:

type Mutation {
  transitionProject(input: ProjectTransitionInput!): ProjectTransitionOutput!
}
input ProjectTransitionInput {
  id: ID!
  changeset: ID
  step: ProjectStep!
  comment: String
}
type ProjectTransitionOutput {
  project: Project!
}

type SecuredProjectStep {
  history: [ProjectStepChange!]!
}
type ProjectStepChange {
  step: ProjectStep!
  by: User!
  comment: String
}

• Does transitionProject() or changeProjectStep() make more sense?
  • These should fully work with changesets
  • Maybe we deprecate updateProject.step for this new mutation as well?

Once this is done we can talk about integrating changeset status and project step workflows.

[CarsonF]

• [ ] The steps given here will replace the current ProjectChangeRequestStatus values.
• [ ] #2273 needs to be replicated for ProjectChangeRequest.status as well.
• [ ] The workflow outlined can be implemented the same way project steps is.