This article includes commonly reported issues and their solutions.
I cannot find log or error details files to troubleshoot an issue.
If you receive any error notifications, click the notifications, click the error message, and then click View to open the JSON representation of the notification. Take screenshots of these notifications.
By default, full logging is disabled because it creates huge files. For more information how to enable Logging when you need it for debugging, see Enable Standard Settings and Advanced Features. If you encounter issues while working with one of the connectors, follow these steps:
Send the annotated log files and screenshots to CA Support to get help with troubleshooting the issue.
To troubleshoot an issue, I would like to send a copy of a flow to CA Support, but it contains sensitive information.
If the flow contains sensitive information, we recommend that you save a copy of the flow as a masked file. Saving a masked file removes the actual data from the flow, while leaving the structure of the flow untouched. This file allows Support to recreate the issue and analyze the flow.
The Save to Masked File menu item in the File tab is hidden by default. For more information how to enable it, see Enable Standard Settings and Advanced Features. Restart CA Agile Requirements Designer after you enable or disable this menu item.
In CA Agile Requirements Designer documentation, we use "path" and "test case" interchangeably: This is because in the case of Agile Central, ALM, and TFS, a test case is nearly always represented as a path in CA Agile Requirements Designer. For Jira, you can represent a test case as a block, path, or flow, respectively.
I logged on to an integration and I configured a project. But I cannot find an expected work item in the tree.
Verify that you are looking at in the correct project tree. Log in to the lifecycle tool's web interface in the browser and check if the work item is indeed in that project.
If the work item is associated with the project, verify that it is organised into the correct (Agile Central) iteration, release , TestPlan (Agile central, TFS) Test Suite (TFS), Test Folder (ALM), respectively.
If you have exhausted the above steps, try to reproduce the issue with logging turned on, as described in this troubleshooting article.
The Jira integration in the General Config window displays entity names in a foreign language or in foreign characters (for example, Chinese, Korean, Japanese).
Log on to the Jira web interface, open your Jira profile, and edit the Preferences. Ensure that "Language" is set to a specific language, for example, English. Do not select "Automatically detect browser setting" when connecting through the CA Agile Requirements Designer integration. CA Agile Requirements Designer is not a web browser, and therefor Jira's language detection defaults to the first language in the list.
When I export Paths, Blocks, or Flows, my Test Cases aren’t exporting.
Verify that you have mapped CA ARD attributes to appropriate attributes for the lifecycle tool. Open the browser, and look at the fields for the lifecycle tool. Verify that when you export, for example, a block, that all block fields are mapped for the item that you are exporting. If no ARD field exists for the mapping, create a Custom Field and map it. If the configuration is highlighted in green, you have mapped the minimum number of attributes. If the configuration is highlighted in red, identify and map missing attributes.