Clarity table (int_external_data) thinks the project in Rally has been closed, however project was never closed in Rally

Products

• Clarity PPM SaaS

Issue/Introduction

Similar to DE80723 identified another scenario where the Clarity table (int_external_data) thinks the project in Rally has been closed, however never closed it in Rally. The Integration Mapping job is not reopening the Rally project and we don’t know how the Rally project in clarity is closed (reset back to 0).
The Project is not coming over (and doesn’t appear in the OOB lookup in Clarity) though they exist as we looked in the database and confirmed.

Query to identify the Rally project is closed according to Clarity:

SELECT DISTINCT
        im.name im_name, 
        ed.code ext_obj_code,
        ed.name ext_obj_name,
        ed.is_active ext_is_active,
        ed.external_opt_id ext_obj_id
FROM   int_external_data ed
        JOIN int_external_attributes ea ON ed.external_attr_id = ea.obj_uuid 
        JOIN int_external_objects eo ON ea.external_object_id = eo.id
        JOIN int_objectmappings om ON eo.code = om.external_object_id AND ed.im_id = om.im_id 
        JOIN int_integrationmappings im ON om.im_id = im.id
        JOIN inv_investments inv ON inv.odf_object_code = om.clarity_object_id
WHERE  ea.name = 'Project'
AND    ea.external_data_type = 'OBJECT'
AND ed.name like 'Scrum %'
order BY ed.name

Steps to Reproduce:

1.     Run the Import Integration Mappings Job to get all the Rally Projects over for a workspace. This should be done using a Rally API Key from a Rally workspace admin.

2.     Use a different Rally user that does not have access to all the Rally projects (not a workspace admin, but can only see a few projects). Put that user's API key in the Integration object for authentication to Rally.

3.     Run the Import Integration Mappings Job again.

4.     Notice that only the Rally Projects that the new user can see will be active and available in the OOB Rally Projects lookup. All the other Rally Projects will be marked as Inactive (int_external_data.is_active set to 0)

5.     Now reset the Integration object back with the good API Key from the Rally workspace admin.

6.     Run the Import Integration Mappings again. This should add back in all the Rally Projects for the workspace, but it will not.  All of those previously inactive Rally Projects will remain inactive, but should have been reactivated.

Environment

Clarity/Rally Integration

Resolution

This defect is resolved by DE80723  - When closing a Rally Project but then reopen, never gets added back into the OOB Rally Project lookup in Clarity.

If the Rally project closed and open again, the fix which we are giving for DE80723 will address this. The existing problem is once the Rally Project is in-active (is_active = 0 in int_external_data table), there was no update happen back in Clarity (is_active =1) again (without changing name). With the provided fix for DE80723, will update the Rally Project as active (is_active = 1 in int_external_data table) if the Rally Project is active now and the provided API key has access. The fix for DE80723 is solving this issue.

Workaround:
- Set up new test integration with same Rally Workspace and the new Integration Mapping Job will pull Rally project into the table and set to active, and successfully pull in the project in Clarity.
- Change the name of the reopen Rally Project in Rally then run the Import Integrations Job, it will update the name and the is_active flag appropriately in the internal Clarity table. This makes it available on the lookup. Then you can change the Rally Project name back to the original name in Rally and re-run the Import Integrations Job again to get the data back to what it should be.