Rally-Jira WIC Connector: Jira Defect is unable to sync with Rally Defect (RallyItemReflector error)

Products

• Rally SaaS

Issue/Introduction

Jira Defect TEST-XXXX is unable to sync with Rally Defect DEXXXX.

Error:

[2024-07-08 16:24:44 Z]  INFO: WorkItemConnector.run - Commencing UPDATE_RALLYFIELDS_AND_OTHER service, obtaining qualifying Jira items

[2024-07-08 16:24:44 Z]  INFO: JiraConnection.getUpdatedArtifacts - Retrieving updated issues using query: project = "TEST" AND type = "Defect" AND "RallyID" > 0 AND updated >= -2m ORDER BY updated ASC

[2024-07-08 16:24:44 Z]  INFO: JiraConnection.getUpdatedArtifacts - Retrieved 1 updated issues in Jira

[2024-07-08 16:24:44 Z]  INFO: WorkItemConnector.run - The UPDATE_RALLYFIELDS_AND_OTHER retrieval of 1 Jira items to process took 0.477 seconds

[2024-07-08 16:24:44 Z]  INFO: RallyItemReflector.reflectUpdatedItemFromOtherInRally - Update Jira Defect ID TEST-XXXXX to Rally

[2024-07-08 16:24:45 Z] ERROR: WorkItemConnector.run - Unable to process all items for the UPDATE_RALLYFIELDS_AND_OTHER service, UPDATE_RALLYFIELDS_AND_OTHER failed to process 147705 successfully, argument of type 'RallyItemReflector' is not iterable

[2024-07-08 16:24:45 Z]  INFO: WorkItemConnector.run - The UPDATE_RALLYFIELDS_AND_OTHER processing of 0 items took 0.122 seconds

Has something changed that will not allow the WIC to sync with Rally issues that have been converted?

Environment

RALLY SAAS

Cause

Connector Version: 5.1.0

Error in Connector Code is fixed and attached.

Resolution

Kindly follow the steps provided below

1. Identify the Problem Location:
   • In the installation directory (e.g., /opt/sw/wic), navigate to the subdirectory named “appkg.”
   • Inside “appkg,” locate the directory named “wicore.”
2. File Replacement:
   • The provided/attached file will overwrite a specific file in this relative path: appkg/wicore/reflector/rally_reflection.py.
   • Adjust the steps as necessary based on your platform (Linux or Windows) and installation directory.
3. Testing and Debugging:
   • Run the connector with a log level of DEBUG (set in the config file).
   • Adjust the UpdateSelector(s) in the JiraConnection of the config. Ensure the connector considers only the item involved in the reported issue (e.g., <UpdateSelector>key = ACMM-XXXX</UpdateSelector>).

Additional Information

There has been no change to the code since the connector since 5.0.22 release in Dec 2023.

This connector is not considered a long-term solution by the Product team, and a new release with this fix is not anticipated.