Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project/Engagement Workflow inside of Changesets #2480

Open
CarsonF opened this issue Jul 27, 2022 · 1 comment · May be fixed by #2488
Open

Project/Engagement Workflow inside of Changesets #2480

CarsonF opened this issue Jul 27, 2022 · 1 comment · May be fixed by #2488
Assignees
Labels
change requests Change Requests feature enhancement New feature or request

Comments

@CarsonF
Copy link
Member

CarsonF commented Jul 27, 2022

While inside of a changesets, the status/step workflow should be different.

These project steps:

  • DiscussingChangeToPlan
  • PendingChangeToPlanApproval
  • PendingChangeToPlanConfirmation
  • DiscussingSuspension
  • PendingSuspensionApproval
  • DiscussingReactivation
  • PendingReactivationApproval
  • DiscussingTermination
  • PendingTerminationApproval

These engagement statuses:

  • DiscussingTermination
  • DiscussingReactivation
  • DiscussingChangeToPlan
  • DiscussingSuspension

These were/are temporary to help facilitate "change to plan" functionality until change requests could be delivered.

We need to update the available transitions for these workflows to skip these values and instead just go straight to the end result.
i.e.

- DiscussingSuspension -> PendingSuspensionApproval -> Suspended
+ Suspended

Obviously status change notifications shouldn't be triggered until the change request is approved.


Workflow around change request approval can happen separately.

┆Issue is synchronized with this Monday item by Unito

@CarsonF CarsonF added enhancement New feature or request change requests Change Requests feature labels Jul 27, 2022
@zkhin zkhin self-assigned this Jul 28, 2022
@zkhin zkhin linked a pull request Aug 1, 2022 that will close this issue
@sync-by-unito
Copy link

sync-by-unito bot commented Mar 1, 2023

➤ Seth McKnight commented:

While inside of a changesets, the status/step workflow should be different.

These project steps:

  • DiscussingChangeToPlan

  • PendingChangeToPlanApproval

  • PendingChangeToPlanConfirmation

  • DiscussingSuspension

  • PendingSuspensionApproval

  • DiscussingReactivation

  • PendingReactivationApproval

  • DiscussingTermination

  • PendingTerminationApproval

These engagement statuses:

  • DiscussingTermination

  • DiscussingReactivation

  • DiscussingChangeToPlan

  • DiscussingSuspension

These were/are temporary to help facilitate "change to plan" functionality until change requests could be delivered.

We need to update the available transitions for these workflows to skip these values and instead just go straight to the end result.

i.e.

- DiscussingSuspension -> PendingSuspensionApproval -> Suspended

+ Suspended

Obviously status change notifications shouldn't be triggered until the change request is approved.


Workflow around change request approval can happen separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
change requests Change Requests feature enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants