...

The user can use any JIRA repository they have available.  Because the content of your JIRA repository will be different, the specific examples in the following exercise instructions are only a guide and example for your actions. It is generally advisable to carry out these exercises in a non-production repository, a “sandbox”, set up for training and practice purposes.

See Video 1.9 for an introduction to the Syndeia Web Dashboard.

Background – JIRA

As envisioned by Intercax, the Digital Thread is composed of inter-model connections between models in different repositories, which Syndeia creates and manages, and intra-model connections between elements in the same repository, which the individual tool creates and manages. As of Syndeia release 3.4, the Syndeia Web Dashboard can extract and display some model information from a Jama Connect JIRA repository. Figure 1 shows a tree view of this information, with labels identifying the Jama Jira element types. Note the different icons. The label color coding indicates how the Jama JIRA element type is mapped to the Syndeia Cloud element types: Repository (green), Container (red), and Artifact (blue).

The Syndeia JIRA integration supports a large number of standard JIRA issue types, including Story, Bug, Task, Improvement, as well as other standard and custom types. Similarly, the Relations table (Step 7) and the Digital Thread Explorer (Step 9 onwards) can display a wide variety of JIRA relations between issues, as well as inter-model connections. A partial list of supported Jama Jira relations include Relates, Blocks, Cloners, and Duplicates. The intra-model connections are not permanently part of the Syndeia Cloud graph; they are extracted and displayed as needed.

This information is important in formulating and interpreting Syndeia graph queries. A more complete diagram of the Jama Jira data model as it is understood by Syndeia is available through the web dashboard help menu on the left.

...