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

Changing event type from "interrupting" to "non-interrupting" should retain properties #4567

Open
fml2 opened this issue Sep 30, 2024 · 3 comments
Labels
backlog Queued in backlog BPMN enhancement New feature or request good first issue Good for newcomers modeling spring cleaning Could be cleaned up one day ux

Comments

@fml2
Copy link

fml2 commented Sep 30, 2024

Problem you would like to solve

I'm always frustrated, when I change the type of a start message event from "interrupting" to "non-interrupting" (or the other way around) and the properties of the event are lost (e.g. the message name).

Proposed solution

Retain all element properties if its type is changed from "interrupting" to "non-interrupting". This should be applied for all element types that have those two sub-types.

Alternatives considered

Without the proposed feature, I have to manually enter the properties again.

Additional context

Depends on bpmn-io/bpmn-js#2249.

@fml2 fml2 added the enhancement New feature or request label Sep 30, 2024
@nikku nikku added BPMN modeling ux spring cleaning Could be cleaned up one day backlog Queued in backlog good first issue Good for newcomers labels Sep 30, 2024
@nikku
Copy link
Member

nikku commented Sep 30, 2024

I can reproduce by replacing a * boundary event with the non-interrupting version:

capture VgEode_optimized

I cannot reproduce by changing an element to be "non-interrupting":

capture 3jE71z_optimized

@fml2
Copy link
Author

fml2 commented Sep 30, 2024

For a start message event (e.g. in a event based subprocess) the properties get lost in both cases.

@nikku
Copy link
Member

nikku commented Oct 11, 2024

Linked upstream bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Queued in backlog BPMN enhancement New feature or request good first issue Good for newcomers modeling spring cleaning Could be cleaned up one day ux
Projects
None yet
Development

No branches or pull requests

2 participants