Skip to content
CA Agile Requirements Designer - 2.6
Documentation powered by DocOps

Troubleshooting

Last update June 27, 2018

How Do I Create an Error Log for CA Support?

Symptom:

I cannot find log or error details files to troubleshoot an issue.

Solution:

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:

  1. Click Home, Settings and go to the Standard Settings tab.
  2. Enable logging for one of the supported integrations:
    • VersionOne Logging
    • CA Agile Central Logging
    • HPE Application Lifecycle Management Logging (ALM)
    • Atlassian Jira Logging
    • Microsoft Team Foundation Server Logging
  3. Reproduce the error. 
    The messages that are thrown by this integration are logged.
  4. Click Help, Save Logs, and select a target directory.
    CA Agile Requirements Designer adds the environment and license details to the log output, and saves the file.
  5. Disable logging after you have tracked down the issue to save disk space.

Send the annotated log files and screenshots to CA Support to get help with troubleshooting the issue.

How Do I Send a Masked Flow File to CA Support?

Symptom:

To troubleshoot an issue, I would like to send a copy of a flow to CA Support, but it contains sensitive information.

Solution:

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.

Troubleshooting Lifecycle Tool Integrations

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.

Why are my Test Cases Not Exporting?

Symptom:

When I export Paths, Blocks, or Flows, my Test Cases aren’t exporting.

Solution:

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.

Example Scenario: I am exporting CA Agile Central user stories as blocks

  1. Open the General Configuration dialog, and open the CA Agile Central tab.
  2. Browse to your project and open the tree.
  3. Select User Story, because you want to export User Stories.
  4. Go to the Block tab for User Stories, because you want to export them as ARD Blocks.
    One or more lines are highlighted in red.
  5. Map CA Agile Central attributes to appropriate CA ARD fields.
    The lines are highlighted in green. You have resolved the conflict.

Example Scenario: I am exporting ARD paths as ALM test casees, and ARD blocks as ALM steps

  1. Open the General Configuration dialog, and open the ALM tab.
  2. Browse to your project and open the tree.
  3. Select test, because you want to export ALM test cases.
  4. Go to the Path tab for tests, because you want to export them as ARD paths.
    One or more lines are highlighted in red.
  5. Map ALM test case attributes to appropriate CA ARD path fields.
    The lines are highlighted in green.
  6. Select design-step, because you also want to export ALM steps.
  7. Go to the Block tab for design-steps, because you want to export ARD blocks as ALM steps.
    One or more lines are highlighted in red.
  8. Map ALM step fields to appropriate CA ARD Block fields.
    The lines are highlighted in green. You have resolved the conflict.

Example Scenario: I am exporting Jira user stories as flows, but there is no suitable ARD field to map one of the attributes

  1. Open the General Configuration dialog, and open the Jira tab.
  2. Browse to your project and open the tree.
  3. Select Issue:Story, because you want to export Jira user stories.
  4. Go to the Flow tab for Issue:Story, because you want to export them as ARD Flows.
  5. Verify that all ALM test case attributes are mapped to CA ARD path fields.
    You cannot find an appropriate field that coresponds to Jira’s Reporter attribute. The Reporter line is highlighted in red.
  6. Click Version Custom Fields.
  7. Create a custom field ‘JiraReporter’ and define your Jira username as the default. You can choose any name for your custom field.
  8. Return to the Jira mapping for Issue:Story, Flow.
  9. Map the Reporter attribute to the custom JiraReporter field.
    The Reporter line is highlighted in green. You have resolved the conflict.

Why Don't I See my Work Item in the Tree?

Symptom:

I logged on to an integration and I configured a project. But I cannot find an expected work item in the tree.

Solution:

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.

How to Set the Character Encoding for my Jira Configuration Window?

Symptom:

The Jira integration in the General Config window displays entity names in Chinese characters.

Solution:

Log on to the Jira web interface, open your Jira profile, and edit the Preferences. Ensure that "Language" is set to a specific language. Do not use "Automatically detect browser setting" when connecting through the CA Agile Requirements Designer integration.

Was this helpful?

Please log in to post comments.