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

Update project and engagement workflow in changeset #2488

Open
wants to merge 10 commits into
base: develop
Choose a base branch
from

Conversation

zkhin
Copy link
Contributor

@zkhin zkhin commented Aug 1, 2022

Fixes #2480

┆Issue is synchronized with this Monday item by Unito

@zkhin zkhin requested a review from CarsonF as a code owner August 1, 2022 17:59
Copy link
Member

@CarsonF CarsonF left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there's some confusion here. The steps listed in the issue would be going away in the future. We need to add transitions to bypass those listed, conditionally based on whether we are in a changeset.
So for example, instead of Active to DiscussingSuspension, it would be replaced by Active to Suspended.

@@ -472,6 +472,11 @@ export class ProjectRules {
type: TransitionType.Neutral,
label: 'Will Not Change Plan',
},
{
to: ProjectStep.ActiveChangedPlan,
type: TransitionType.Changeset,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would probably be better to use a separate property here. The transitions inside of changesets still could have "types" so we don't want to block or overload that functionality. Maybe changeset: true or inChangeset: true.

@zkhin zkhin force-pushed the feature/2480-update-project-engagement-workflow-in-changeset branch from fc8fed2 to 22f7b55 Compare August 2, 2022 15:51
@@ -20,6 +20,7 @@ import {

interface Transition extends EngagementStatusTransition {
projectStepRequirements?: ProjectStep[];
inChangeset?: boolean;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add inChangeset prop and it will have three states now.

  • true: transition will be available only in changeset mode
  • false: transition will be available not in changeset mode but in the normal workflow
  • undefined: transition will be available for both workflows.

@zkhin zkhin requested a review from CarsonF August 2, 2022 16:25
zkhin and others added 9 commits August 12, 2022 16:06
This should happen automatically when the changeset is approved, but it shouldn't be shown to user
It's the last forward step & this groups the terminate transitions together
Users are free to make these transitions as they are not applied
until the changeset is approved by these approvers.
Inside changeset you can do
Active -> Suspend -> Active
instead of
Active -> Suspend -> ActiveChangedPlan
@CarsonF CarsonF force-pushed the feature/2480-update-project-engagement-workflow-in-changeset branch from 22f7b55 to 2bc8581 Compare August 15, 2022 21:10
@CarsonF
Copy link
Member

CarsonF commented Aug 16, 2022

Hey @zkhin I made some changes here. Would you read through my commits and apply the same logic to the engagement workflow?

@zkhin
Copy link
Contributor Author

zkhin commented Aug 23, 2022

Hey @zkhin I made some changes here. Would you read through my commits and apply the same logic to the engagement workflow?

Sure, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Project/Engagement Workflow inside of Changesets
2 participants