-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Improve semantic ordering in replace / append menu for "implementation" #1621
Labels
Comments
Moving to backlog as we cannot immediately act upon this; needs further discovery. |
Ordering is already pluggable today:
|
This was referenced Jan 15, 2023
Merged
Feedback shared via https://github.com/camunda/product-gaps/issues/73: As a user I'd like to replace from one event type to another without loosing the event definition contents (i.e. message configured). |
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a priority < 0 to hide elements from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a priority < 0 to hide elements from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a rank < 0 to entries to hide them from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
that referenced
this issue
Feb 3, 2023
Ensures these are more prominently featured in replace + create/append anything menus. Related to #1621
nikku
added a commit
that referenced
this issue
Feb 3, 2023
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a rank < 0 to entries to hide them from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a rank < 0 to entries to hide them from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 3, 2023
Allows integrators to assign a rank < 0 to entries to hide them from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
to bpmn-io/diagram-js
that referenced
this issue
Feb 6, 2023
Allows integrators to assign a rank < 0 to entries to hide them from the initial list of items. These items will appear once searched for. Related to bpmn-io/bpmn-js#1621
nikku
added a commit
that referenced
this issue
Feb 6, 2023
Ensures these are more prominently featured in replace + create/append anything menus. Related to #1621
nikku
added a commit
that referenced
this issue
Feb 6, 2023
nikku
added a commit
that referenced
this issue
Feb 7, 2023
Ensures these are more prominently featured in replace + create/append anything menus. Related to #1621
nikku
added a commit
that referenced
this issue
Feb 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
As a tool we want our users to get work done as efficiently as possible. Upgrading tasks via the replace menu to make them executable is an important part of the modeling interaction.
To date, however, we don't provide clear guidance to the user on what is possible / relevant. In fact, considering the options provided by the change / replace menu, you can see that the order is historically grown / accidental:
Describe the solution you'd like
Describe alternatives you've considered
Remove discouraged options (i.e. "manual task") would be a "execution only" option.
Do not have a fixed order, but also incorporate "recently used" into the mix (cf. know the context).
Additional context
Getting this right contributes to "speed up time to implemented" (https://github.com/camunda/web-modeler/issues/860).
We shall consider this in the context of the new change / append UIs shipping with the web modeler. There we can rely on search for rare items to be discoverable.
This is addressed through #1627.
The text was updated successfully, but these errors were encountered: