Pipeline problems

[Volodymyr]

Hello,
Maybe I just didn't find this feature, but how to change order of created Pipeline Stages, in kanban view (Opportunity). It looks like this feature is missing in version 10.0.

[yuri]

Pipeline stages can be reordered using the actions in the dropdown menu in the Stages list panel of the Pipeline detail view.

The reordering is limited by the order of the Status field options. For example, if there are two statuses, Open and Closed, each with multiple stages, you cannot move stages belonging to the Closed status before stages belonging to the Open status.

https://docs.espocrm.com/general/pipelines/

[Volodymyr]

Thank you for the explanation, but it turns out there is a major flaw or a bug in how Pipeline Stages reordering works in version 10.

1. No Drag-and-Drop: There is absolutely no Drag-and-Drop capability in the Stages list panel within the Pipeline detail view. I've tried multiple times, cleared the cache, and verified global Stage field options order—rows are completely static.

2. Broken Relations on Re-creation: Since reordering isn't working, the only way to arrange stages chronologically is to delete them and add them again in the correct order. However, doing so completely breaks the data integrity.

3. The ID Issue: When a stage is deleted and re-added, EspoCRM generates a brand-new ID for that Pipeline Stage record. As a result, all existing Opportunities remain linked to the old, now non-existent ID. Instead of the stage name, the Opportunity detail view displays a broken hash-string (e.g., 6a495ad5d99374759), and the Kanban board appears empty.

It forces us to manually perform Mass Updates on dozens of deals just to fix the broken links after a simple layout adjustment.

Could you please consider adding a proper 'Reorder' action button or enabling standard sorting for the Pipeline Stages panel? Breaking database relations during a simple stage reshuffle definitely feels like a bug.

[yuri]

> 1.

There's no drag and drop. It's possible to move them with dropdown actions.

> 2. Broken Relations on Re-creation

It's expected and normal.

> 3. EspoCRM generates a brand-new ID

It's how it should work.

----

You define the status field options. For example you can have only two status options for simplicity: Open, Closed.

Then, you create a pipeline with stages. You can re-order them as you want without braking anything. The only limitation is that you cannot have stages mapped to Open after stages mapped to Closed (what I described above). It was made to prevent creating pipelines like Closed > In Progress > Draft.

Please avoid jumping to conclusions like "turns out there is a major flaw" or "breaking database relations...". They come off bit harsh.