Support for Multiple Opportunity Pipelines Based on Opportunity Type

[oddieis]

Scope & Context

We would like to request improving opportunity management in Twenty CRM.
The ticket is about enabling different opportunity pipelines, allowing users to define distinct sets of stages based on the opportunity type.

Current behavior

Currently, all opportunities follow a single, fixed set of stages.
Many CRMs allow users to define multiple pipelines with different stage progressions that align with different types of opportunities.
Since users cannot currently define separate pipelines in Twenty CRM, they are forced to find workarounds.

Additionally, users cannot hide the standard Opportunity object, meaning they must work within its constraints rather than defining custom pipeline types.

Expected behavior

Users should be able to create multiple opportunity pipelines, each with its own set of stages.
When creating an opportunity, users should be able to select a pipeline that determines the opportunity's progression.

For example:

• A new customer opportunity follows an onboarding flow with specific stages.
• A prospective customer for Product A follows a different sales process with unique stages.
• A new partner follows an entirely separate partnership approval process.

Each of these scenarios should be supported by separate pipelines with their own custom-defined stages.

Technical inputs

• Modify the opportunity model to allow multiple pipelines with distinct stage configurations.
• Create an interface for defining and managing pipelines.
• Update the opportunity creation flow to allow users to select a pipeline.
• Ensure that opportunities follow the correct pipeline with appropriate stage progression.
• If possible, allow users to hide the standard Opportunity object if they prefer to use custom pipelines.

[Bonapara]

What you could do as a workaround:

• Create a different Select field with your Pipeline2 steps
• Create a second filtered view filtered on the values contained in this select
• Hide the pipeline 1 select values

We will work on a more robust solution mid-term.

[oddieis]

This issue can generalized, so it isn't just about pipeline selection.

We need conditional field accessibility and field groups too.

Eg if I select a certain value in a field that should allow the enabling or disabling of other related fields. This will allow the fields for opportunity type A to only be visible when the relevant opportunity type is selected. And those fields should be grouped together.

The same applies when opportunity type B is selected - it's relevant fields should be only accessible then and should be grouped together.