Feature Request

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add support for model element properties management

    Add support for model element properties management.
    User can add additional properties to a kind of model element
    for the Use Case model element,
    user can add, for example, post conditions, pre-conditions, business trigger, version, ...
    then whenever a new use case added to the model these new properties are accessible from the properties panel ...

    In summary, extend-ability of the model elements per model element type.

    The customized added properties can be used for documentation and code generation.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bug: It is impossible to reuse self messages across multiple time-sequence diagrams.

    It is possible to reuse regular messages by drag & drop them into a new diagrams, but it does not work for self messages.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. ERD diagram automation: "ReferenceTo" property combo should be prefilled with fields of the entity is already relates to.

    Imagine you have 2 entities with 1-to-many relation. That means that the second should have a key that references to the first entity. As soon as there is already relation in diagram - list of possible fields can be already obtained and displayed in dropdown-combo for "ReferenceTo" property.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Patterns Library (Templates)

    Patterns libraries would be really great, just like in StarUML 5. User should be able to apply pattern templates to a model/design, as well as create custom pattern templates that can easily be reused across several models and projects

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Snap to grid

    It would be nice to have a "snap to grid" option so it becomes easier to position elements next to each other.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow hyphens for naming subystems and swimlane

    In German we use hyphens for combining words coming from different languages, like "Bürger-Client" or "Compliance-Manager".
    When entering names like that in the diagram area, the StarUML does not allow it. Workaround for this is writing the name directly in the element's properties area.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Refactoring of diagram would be very handy and exclusive

    I always felt the lack of a way of split automaticly a complex diagram in short ones. It would be amazing. Mainly in Sequence and Class Diagrams. This reduce complexity a lot.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Don't restrict the left and top side of the canvas

    Please make the canvas extendable to the left and the top - or make the Rectilinear lines not breaking anymore when moving the package around them. :)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Use-case actor (stick figure), request additonal/selectable graphic

    In real use-case diagrams, the Actors are not always People, they are often some external system. I request an option to represent a non-human actor, anything other than a stick-figure.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. RMP packages for Fedora

    If you build packages for Fedora then a lot of users will be happy and ready to buy your product.

    105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow to collapse all items inside of the explorer

    Currently in the explorer window you need to click each single item in order to collapse all of them. Would be great to allow collapse items inside of the parent node or all of the items currently displayed inside of the explorer view.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for Delphi under windows and lazarus under Linux

    It is suprising to me that having been written in Delphi it does not support Delphi and Linux roundtrip

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow for code generation in gulp, grunt or VS build step

    It would be nice to be able to incorporate code generation as a part of a gulp/grunt build step. This would allow for the time investment to generate Typescript/JS classes (and C#) in order to easily match API generation. As a worst case, a T4 text template API to work with staruml projects would suffice.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Fragmentation Support

    Developers needs to design their model and share between each other. Like Rational SW this tools need to make one model into separated fragments and can be synchronized

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow per-attribute show/hide in a class diagram

    Sometimes I show a class in several class diagrams. I would like to be able to selectively show the attributes of the class that are relative to that class diagram, and hide all the others.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. support attribute's comment and can see it in the diagram.

    for some attribute, we should comment it with chinese language for discuss the model.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support for better layout algorithms using https://github.com/OpenKieler/klayjs

    The layout algorithm for the diagrams do not layout the labels and are somewhat bad. Perhaps the use of this library would help the quality of the diagrams.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Ability to import an icon set/font like FontAwesome or an image for use as objects in the editor.

    Some things may be better expressed through images or different icons. This may even need the addition of a sort of "sandbox" diagram where anything goes.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. customize the toolbox

    I'd like to be able to add items to the toolboxes that don't come there by default.. like a component to the use case diagram toolbox or something like that

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feature Request

Feedback and Knowledge Base