Lane naming only possible with at least 2 lanes

[Ainges]

Describe the Bug

If a new pool is created, the individual lane cannot be named. A workaround is to add a second lane. If this lane is then removed again, the name of the first lane is retained.
Due to this behaviour, I assume that this is a bug and not an intended behaviour.

Steps to Reproduce

1. Create new Model
2. Add Pool
3. Try to give the Lane a name

Expected Behavior

I would expect that even in a pool where there is only one lane, I would be able to name it.

Environment

• Browser: Chrome Version 130.0.6723.71 (Official Build) (arm64)
• OS: MacOS 15.1
• Library version: demo.bpmn.io on 05.11.2024

[philippfromme]

When creating a participant no lane will be created until you create a "second" lane. Would you expect a single lane to always be created?

[philippfromme]

As a workaround, you can create a "second" lane and then remove it:

[Ainges]

Hello, thanks for the quick reply. Yes, I already know the workaround as described above. However, I would actually expect to be able to assign a name for the lane directly.

[nikku]

@Ainges What is your use-case to assign a name for the only lane within a pool? Could you elaborate? This is simply not implemented on our end, because we don't see the use-case for this.

[Ainges]

Thank you for your interest.
Of course, using the workaround is not a major issue. However, during a lecture last week, the question arose as to why it’s necessary. As I understand it, the labeling of the pool is synonymous with the process being executed. Even if there is only one role within the process, we label it explicitly. This led to the question of why the approach is so cumbersome and whether it might be a bug. For this reason, I created the ticket.