This works only if any of the connected model elements is missing from diagram: dragging an existing relationship to the diagram adds it.

However, if both model elements are present then there is no way to add an existing relationship to the diagram. This is frustrating, because this is a frequent scenario:
- relationship may have been added through another diagram, now it needs displaying on original diagram
- relationship may have been deliberately removed from diagram (to lessen clutter, etc.), but must be redisplayed after all

current workaround: remove at least one connected model element, then drag relationship to diagram. however, this is a "poor man's" solution, because:
- it will add other relationships (possibly unnecessary on current diagram)
- all formatting, connector routing, etc. is lost, must be done again

this is a continuation from
staruml.uservoice.com/forums/245359-feature-request/suggestions/6073176-need-feature-to-add-relationships-to-diagram-when

The markdown support per element in the "Model Explorer" a very useful feature, where we can keep analytical information about our elements.

However I noticed that I can't use the markdown link notation in order to provide direct links between the markdown text and elements that I have in the "Model Explorer".

I think it would be very useful to be able to add such multiple links in starUML's markdown support. When someone clicks on the markdown link he should be transferred either to the selected Element through "Model Explorer" either to the the proper link of the element when using an exported code i.e. "Export->HTML Docs...".

Take as example the following project, where the "Model-B" UMLModel it has a description where I want to have 2 links. One to UMLModel "Model-A" and another one to UMLClassDiagram "Main". It would make perfect sense to use the "id" of each element as target to markdown link, and then when someone clicks on the markdown link through starUML, to actually select the corresponding element with that "id" in "Model Explorer". On the other hand when someone clicks on the markdown link in an exported version of the project i.e. "Export->HTML Docs...", he should be linked to the corresponding element via the proper URL link (e.g. when exporting to translate properly the unique "id" to a unique URL path; the URL path for the element with that "id").

Such a feature would help to use MARKDOWN to describe and group textually different elements together, with direct selection/access from the markdown section (e.g. from the overview description of a UMLModel).

However this would require an extra right-click option at the "Model Explorer" called i.e. "copy Internal Link". Thus, in the provided example below, when someone selects an element like the UMLModel "model-A" and then right-click, "copy Internal Link" the value "AAAAAAFF+qBWK6M3Z8Y=" should be copied to clipboard. With this value a markdown url can be created like: "Model-A", which corresponds to a link-phrase "Model-A" which when pressed leads to the "model-A" UMLModel element (either from inside the starUML software, either by updating the URL i.e. from any other exported version like "HTML Docs...")

Example project:

{

"_type": "Project",

"_id": "AAAAAAFF+h6SjaM2Hec=",

"name": "markdown link test",

"ownedElements": [

    {

        "_type": "UMLModel",

        "_id": "AAAAAAFF+qBWK6M3Z8Y=",

        "_parent": {

            "$ref": "AAAAAAFF+h6SjaM2Hec="

        },

        "name": "model-A",

        "ownedElements": [

            {

                "_type": "UMLClassDiagram",

                "_id": "AAAAAAFF+qBtyKM79qY=",

                "_parent": {

                    "$ref": "AAAAAAFF+qBWK6M3Z8Y="

                },

                "name": "Main",

                "defaultDiagram": true

            }

        ]

    },

    {

        "_type": "UMLModel",

        "_id": "AAAAAAFuE0OEPewmZ74=",

        "_parent": {

            "$ref": "AAAAAAFF+h6SjaM2Hec="

        },

        "name": "Model-B",

        "documentation": "This is Model-B and its a bit different than [Model-A](AAAAAAFF+qBWK6M3Z8Y=) which have the UMLClassDiagram [Main](AAAAAAFF+qBtyKM79qY=)."

    }

]

}