ConnectAll - Changing issue type in Jira creates relationships with multiple automations and multiple artifacts in Rally

Products

• Rally SaaS

Issue/Introduction

 Changing the issue type in Jira creates relationships with multiple automations and multiple artifacts in Rally.  It also changes the artifact back to the original issue type after a couple of automation runs.

 

An example: 

• If a user creates a story issue in Jira, and that issue type is associated with a user story automation for Rally.   

• The user changes the Jira issue type to bug, which is on a different CA automation, then two records are created in Rally. 

• When the user modifies the Rally user story record, then ConnectAll will revert the issue type back to story in Jira. 

• Additionally, when the defect on Rally is modified, then the Jira issue will be reverted back to a bug again. 

• We expected the original user story record on the Rally side to become disconnected from the item in Jira, but ConnectAll retains the record relationship as one-to-many rather than one-to-one.

   

Steps to Reproduce: 

1. Create 2 automations from Jira to Rally (Jira is source of truth).  

   1. Jira Bug to Rally Defect

   2. Jira Story to Rally User Story

2. Create a Jira Story (ex: TEN-1) and allow the Story automation to create a new User Story in Rally (ex: US1).

3. Change the Jira Story to a Jira Bug (no other changes) (Still TEN-1) and run the Story Automation - no changes

4. Run the Jira Bug Automation and see the new Defect created in Rally (ex: DE1) 

5. Change the Name on the Rally Defect (DE1) and run the defect automation and see Jira TEN-1 Name Change - so far so good

6. Change the Name on the Rally User Story US1 and run the Story automation and see the TEN-1 artifact type change to STORY

Expected Results: 

• The Jira artifact remains a defect.

Actual Results:

• The Jira Artifact type changes back to a Story

Environment

3.8.0

Resolution

DE173125 fixed in future release