Skip to content

Make create/append actions context aware #3

@nikku

Description

@nikku

Is your feature request related to a problem? Please describe

As a user I'm confronted with a large list of choices in the create, replace, and append menu. While usually I just want to continue to model the way I am used to (i.e. service task only in microservice orchestration case).

Describe the solution you'd like

Rather than showing a huge list of options, only show what the user is likely to use; make everything else discoverable as a second look (i.e. via search or view more).

Describe alternatives you've considered

Stick to "static" nature of these menues.

Additional context

Raised as feedback by @marstamm, too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogQueued in backlogenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions