One use case supported by the Syndeia JIRA interface is to take a multi-level SysML structure, which could be activities, blocks or requirements, and use it to create a corresponding multi-level issue structure in JIRA, each SysML element connected to its corresponding JIRA issue. Using these connections, each SysML element can access the corresponding JIRA issue, including people assigned and time to completion.
In the JIRA Tutorial MagicDraw project, in the JIRA Activity Structure package, a multi-level activity structure has been created. The model as it appears in the containment browser is shown. In the two activity diagrams in figure below, we can see that the top-level activity, UAV Project, is decomposed into three actions typed by the activities Task 1, Task 2 and Task 3. Task 1 is further decomposed into three actions typed by Subtask 1A, Subtask 1B and Subtask 1C.
In the Syndeia dashboard, Settings tab, set Default Issue Type under the JIRA tab to Task. This will result in new issues being created as Tasks.
In the Syndeia dashboard, Connection Manager tab,
1. select the JIRA repository in which the new task structure will be created.
2. Expand the Projects list.
3. Set the Connection Type to Reference
4. Drag the top-level activity UAV Project (in the SysML model shown in the left pane) on to the JIRA project in which the Tasks are to be created.
5. In the options window that appears, select Generate issue(s) and create reference connection(s).
6. Click OK.
The new reference connections are shown. Note that each activity used in UAV Project is now connected to a corresponding JIRA task issue.
Close the Syndeia dashboard. From the MagicDraw containment browser, right-clickthe activity Task 1 and select Syndeia → Open Connected Artifacts. The corresponding JIRA issue opens in the JIRA interface.
Note at the bottom of the figure, this issue is shown as linked to the issue for the higher level activity UAV Project and the three lower-level activities, Subtask 1A, Subtask 1B and Subtask 1C. While JIRA does not support an "issue hierarchy" exactly like the activity structure in SysML, Syndeia uses the "relates to" issue link to create a corresponding network of connections.
This process just demonstrated creates reference connections from SysML to JIRA for activity, block or requirements structures. A more powerful set of connections can be made if the SysML block structure is composed of blocks with the applied stereotype <<JIRA_Issue>> and the Model Transform connection type is used for the drag and drop action. In this case, the connection created between each block and its corresponding issue are of the same type as in Section 2.17.2, where attributes such as status, assignee, and so forth can be compared and updated between SysML and JIRA. In this use case, the SysML block structure and connected issues can act as a Work Breakdown Structure within the SysML model for project management purposes.

Browser not supported