Page Comparison

...

1. Open the SysML project Syndeia_JIRA_Mapping_Tutorial.mdzip (get it here -SysML Models, Profiles and Mappings), right-click the JIRA package, and launch the Syndeia dashboard
   

2. Go to the Mappings tab.

   Anchor
   _Hlk501357103 _Hlk501357103

   The first task will be to create a new mapping using existing artifacts.

   1. Right-click SysML-JIRA under Mapping Groups in the left column and select Add Mapping. Initially, the window should appear similar to Figure 1.

      

      Figure 1 Syndeia dashboard, Mappings tab, Adding Mapping to SysML-JIRA Mapping Group
      

   2. Modify the Mapping
      

      1. Change Name to Activity – New Feature (no attributes)
         

      2. Change Description to SysML Activity - JIRA New Feature with no attributes
         

      3. Change Source Artifact Type to Activity, using pull-down menu
         

      4. Change Target Artifact Type to New Feature, using pull-down menu
         

      5. Set Structure Level to CHILDREN_RECURSIVE, using pull-down menu
         

      6. Set Include Attributes to Exclude Attributes, using pull-down menu
         

      7. The window should look similar to Figure 2.
         

         

         Figure 2 Syndeia dashboard, Mappings tab, Adding Mapping to SysML-JIRA Mapping Group, part 2
         

      8. Click Save Mapping at bottom of right side (scroll down if necessary).
         

3. Use the new Mapping you just created
   

   1. Go to the Connection Manager tab. Open a JIRA repository in the right column.
      

   2. Drag the Feature E activity in the SysML model into a JIRA project
      

   3. A small pull-down menu will appear on the Syndeia dashboard, as Figure 3, showing the possible mappings available for an activity dragged into JIRA.
      

      

      Figure 3 Connection Manager while creating new JIRA issue with new mapping
      

   4. Select Activity – New Feature and click OK.
      

   5. Expand the Syndeia Demo Box Project and Reported by me folder. Check that a new JIRA issue of type New Feature has been created with default attribute values assigned by JIRA.
      

4. The second task is to create another new mapping, this one with attributes shared between the SysML and JIRA elements. We will use the Clone Mapping command rather Add Mapping. Clone Mapping saves time when not all features of the new mapping need to be modified.

   1. Right-click Activity – New Feature under Mapping Groups/SysML - JIRA in the left column and select Clone Mapping
      

   2. Initially, the window should appear similar to Figure 4.
      

      

      Figure 4 Syndeia dashboard, Mappings tab, cloning a mapping in the SysML-JIRA Mapping Group
      

   3. Modify the Mapping
      

      1. Change Name to Activity – New Feature (Attributes)
         

      2. Change Description to SysML Activity - JIRA New Feature with attributes
         

      3. Keep Source Artifact Type as Activity and Target Artifact Type as New Feature
         

      4. Set Structure Level to NO_CHILDREN, using pull-down menu
         

      5. Set Include Attributes to Include Attributes, using pull-down menu
         

      6. Click the + sign box under the Stereotypes table.
         

      7. A Select stereotype window will open. The window should look similar to Figure 5 (review Video 1.8 on SysML Stereotypes, if needed).
         

         

         Figure 5 Syndeia dashboard, Mappings tab, modifying the cloned mapping, part 1
         

      8. Select JIRA_Artifact. This choice will appear in the Select stereotype box on the right.
         

      9. Click Retrieve Available Attribute Definitions below the Attribute Definition Mappings table
         

      10. Click the + box below the Attribute Definition Mappings box.
          

      11. In the new row, select Priority (Priority) on the right (Target) side of the table, using the pull-down menu
          

      12. In the new row, select priority (priority) on the left (Source) side of the table, using the pull-down menu
          

      13. Repeat steps xi through xiii for Summary. The final table should look like Figure 6.
          

          

          Figure 6 Syndeia dashboard, Mappings tab, modifying the cloned mapping, part 2
          

      14. Click Save Mapping at bottom of right side (scroll down if necessary).
          

5. Use the cloned Mapping you just created
   

   1. Go to the Connection Manager tab. Open the JIRA repository you used above in the right column.
      

   2. Drag the Feature E JIRA issue created earlier from the JIRA column into an empty SysML package, e.g. J3.
      

   3. A small pull-down menu will appear on the Syndeia dashboard, as in Figure 7, showing the possible mappings available for an activity dragged into JIRA.
      

      

      Figure 7 Connection Manager while creating new SysML Activity with cloned mapping
      

   4. Select Activity – New Feature (Attributes) and click OK.
      

6. A new activity (named Feature E) should appear under J3 on the SysML side. It will have the <<JIRA_Artifact>> stereotype in addition to Activity and all the tag values associated with that stereotype. However, only the two JIRA attributes mapped in the Activity – New Feature (Attributes) mapping (i.e. priority, summary) have been populated in the SysML element from the JIRA issue (see Figure 8).
   

   

   Figure 8  New SysML activity created by cloned mapping
   
   Note that SysML activities do not normally have any place to receive the JIRA attributes. Because the <<JIRA_Artifact>> stereotype was chosen in the new mapping definition, the new activity was created with that additional stereotype and tag values ready to receive the desired JIRA attributes.
   

7. Change priority from Major to Minor in the JIRA issue created from Feature E (named SDB-1837 in our example) through the JIRA web interface

   1. Find the connection between the JIRA Issue and the new SysML activity (J3::Feature E) in the Connection Browser.
      

   2. Right-click the connection and select Compare Source and Target.
      

   3. The Comparison Result tab should appear similar to Figure 9.
      

      

      Figure 9 Comparison Result tab after modifying JIRA issue priority
      

   4. Return to the connection in the Connection Browser and select Sync Target to source and update the priority tag value on the SysML block to Minor.
      

   5. Repeat the comparison and see that all differences have been resolved by updating the SysML model from JIRA