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

Collapse sub process does not move sequence flow descriptions #2993

Closed
rweisleder opened this issue Jun 17, 2022 · 2 comments
Closed

Collapse sub process does not move sequence flow descriptions #2993

rweisleder opened this issue Jun 17, 2022 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@rweisleder
Copy link

Describe the bug

When collapsing a sub process, sequence flow descriptions are not moved to the sub process diagram.

Steps to reproduce

  1. Create a new BPMN diagram for Camunda Platform 7
  2. Create a simple process with start event, activity of type "Sub process (expanded)", and end event
  3. Inside the sub process, create a simple process with start event, activity, and end event
  4. Add a name for a sequence flow inside the sub process

The process looks like this now:
image

  1. Change the activity type from "Sub process (expanded)" to "Sub process (collapsed)"

After step 5, the name of the sequence flow remains in the diagram of the main process. The main process looks like this now:
image

Expected behavior

The name of the sequence flow should be moved to the diagram of the sub process.

Environment

Camunda Modeler system information

  • Version: 5.0.0
  • Operating System: Windows 10 amd64
  • Plugins: BPMN Linter, bpmn-js Token Simulation, Transaction Boundaries
  • Execution Platform: BPMN - Camunda Platform 7

Additional context

No response

@rweisleder rweisleder added the bug Something isn't working label Jun 17, 2022
@marstamm
Copy link
Member

Hi @rweisleder , thanks for opening this issue.

Seems like this was already addressed with bpmn-io/bpmn-js#1617 in bpmn-js, but not yet released in the Modeler itself. This issue will be fixed with the next release

@marstamm marstamm added the fixed upstream Requires integration of upstream change label Jun 17, 2022
@nikku nikku added this to the M54 milestone Jun 18, 2022
Skaiir added a commit that referenced this issue Jul 8, 2022
transitive deps:

`bpmn-js-properties-panel@0.15.1`
Closes #2989, #3003, #2725, #2920

`properties-panel@0.15.0`
Closes #2990

`bpmn-js@9.3.1`
Closes #2993
@Skaiir
Copy link
Contributor

Skaiir commented Jul 8, 2022

Closed via bc8b748

@Skaiir Skaiir closed this as completed Jul 8, 2022
@bpmn-io-tasks bpmn-io-tasks bot removed the fixed upstream Requires integration of upstream change label Jul 8, 2022
Skaiir added a commit that referenced this issue Jul 8, 2022
transitive deps:

`bpmn-js-properties-panel@0.15.1`
Closes #2989, #3003, #2725, #2920

`properties-panel@0.15.0`
Closes #2990

`bpmn-js@9.3.1`
Closes #2993, #2859
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants