Issues

This chapter covers Design Rule Check (DRC) and Issue concepts, the Issues pane, and how to view/create Issues in Capital Teamwork.

Restriction: The Capital Team Collaborator license must be assigned to your user account to access the Issues workflow. See "Licensing Options."

Issues Overview

The system runs background DRCs on designs or at the build-list level. You can configure FEM tasks to run DRCs at regular intervals, or click Submit DRC Task on the Build List Details pane to run on-demand. Tasks check all designs/build lists modified since the last run, then run the Capital DRCs or application DRCs specified in capital_install\config\automated-drcs-task-configuration.xml.

Issues — an Issues container is associated with DRC failures, configurable in the Capital software to track and override specific DRC failures and understand violation quantity/status. See "Track and Override Design Rule Check Failures Using Issues" in the Capital Design Tools - Common Functions User Guide.

You can configure how Issues are managed after a DRC run via automated-drcs-task-configuration.xml:

• Preference to generate an Issue if a DRC reports a failure.
• Preference to automatically delete all Issues not in a certain status.
• Category and release level of generated Issues.
• Preference to close resolved Issues.
• Status of closed Issues.

DRC reports are collected and stored as additional design data; DRC failures are created as "Issues" to track/resolve violations. DRC failures with identical content are created as individual duplicate Issues.

CAUTION: If a DRC violation message is identified for an existing Issue in systems using different languages, the system treats the violation as different and creates a duplicate Issue.

You can also create Issues manually (relating to DRCs or known problems) and assign them via the Assignee field — see "Creating Issues." To resolve Issues, open the design in the Capital Project Manager User Guide and display events for Issues in the Audit Trail dialog box.

Release Level Behaviors

With the "Issues - Set Release Levels" user permission, you can select Release Level Behaviors to manage DRCs and Issues on designs/build lists:

• Batch DRC Run — Enables DRC tasks for specific release levels defined on build lists. If the release level permits a DRC run, Issues are generated per automated-drcs-task-configuration.xml. Output is listed with the build list on the Attachments tab.
• Comments Editing — Enables editing Issue comments.
• Issue Closed — Issue release level auto-assigned to an Issue linked to a fixed DRC failure.
• Issue Editing — Enables control over editing attributes/user properties for Issues.
• Issue Opened — Issue release level auto-assigned to an Issue linked to a new DRC failure.
• Issue Overridden — Release level assignable to an Issue to ignore its linked DRC failure when saving/transitioning a design or rerunning DRCs in the Capital design tools. Tip: You must also select the "Ignore DRCs with overridden Issues when" project preference. See "Edit Project User Permissions" in the Capital Access Manager User Guide.

See "Creating a Release Level for a Project" to create release levels for Issues.

Issues Tabs

The Details pane for the Issues workflow shows the Filter field and a list of Issues reported after DRC runs. Selecting an Issue displays tabs: Details, Properties, Comments.

Note: If object links display in the Details field, click the hyperlink name to view the object's attributes/properties in the Details popup. Administrators can configure a plugin to display specific attributes/properties.

Icons let you create Issues, edit/delete multiple Issues, search for Issues, and toggle list/table view — see "Using Issues."

Details Tab — attributes:

• Issue ID — Auto-generated identifier.
• Category — Category of the DRC that identified the violation.
• Headline — Description of the violation.
• Details — Additional comments/notes for resolving the Issue.
• Assignee — User assigned to resolve the Issue.
• Status — Current release level; dropdown selects the next transition level, per the "Engineering Change Order Editing" behavior.
• Created / Modified — Timestamps.
• Severity — Error, Warning, or Information level of the DRC failure.
• Container — Associates the Issue with a design or build list.

Tip: To ensure severity displays correctly across systems using different languages, configure the allowedValues in issueconfig.json for each client, such as Rating and Link — see "Configuration JSON Files."

Properties Tab — user properties from the source application; delete/add as Name/Value strings — see "Using Properties."

Comments Tab — add multiple comments with image attachments/links — see "Using Comments."

Using Issues

Covers creating and associating Issues with build-list/design containers, and editing Issue properties/comments.

Restriction: Refresh the web page or start a new Capital Teamwork session to activate permission/domain access modifications.

• To create, delete, edit, and change the release level of Issues, assign the appropriate Issues permissions to your user account — see "Edit Project User Permissions" in the Capital Access Manager User Guide.
• Without domain access to a design or build list in an Issue, the Issue does not display in the Issues workflow — see "Domain Restricted Visibility" in the Capital Access Manager User Guide.

Creating Issues

Prerequisite: A project is selected.

Procedure:

1. Issues workflow — Issues from the last DRC run display below the Filter field.
2. Click Create New Issue icon → new Details pane with blank fields.
3. Specify attribute/property values (mandatory fields marked *; Release Status defaults to Draft).
4. In the Details field, type a description, format with the Edit toolbar, insert images/links.
5. (Optional) Associate the Issue with a design or build list container — see "Associating Issues With Containers."
6. (Optional) Fill in Attachments and Properties tabs — see "Common Tasks."
7. Click Create to save the Issue.

Associating Issues With Containers

Associate an Issue with a design or build list container, or change its container.

Prerequisite: An Issue is selected below the Filter field.

Procedure:

1. Click the Container ellipsis (...) → Select Container dialog box.
2. Select the Design or Build list radio button (available designs/build lists in the project are listed).
3. Use the Design Type / Build List Type dropdown to filter by type.
4. (Optional) Type a filter text string to narrow results.
5. (Optional) Search: click the Search Criteria icon, specify attributes, click Search/Reset/Cancel.
6. Select a container from the results and confirm — the selected container link displays in the Container field.

Editing Issues

Edit an Issue in List or Tabular view; edit multiple Issues simultaneously via Batch Edit mode.

Restriction: Deleting an Issue is immediate and cannot be recovered.

Prerequisite: An Issue is selected below the Filter field.

Procedure (choose the action):

If you want to...	Do the following...
Edit one or more Issues simultaneously (Batch Edit mode)	More Actions dropdown → Batch Edit icon. Select Issues individually, via Shift+click range, or Select All. Edit attributes/custom properties on the Details tab and click Update to apply to all selected; or Delete/Export as CSV. Edits apply to the Capital database and Batch Edit mode closes.
Edit the details of one or more Issues	Details tab → edit attribute/custom property fields (use Batch Edit for multiple). Fields with a common value across selected Issues show that value; differing values show --Multiple Values--. Read-only fields (must be unique per Issue): Issue ID, Headline, Details, Created, Modified. Editable default attributes: Assignee, Category, Container, Custom Date field, Custom Check Box field, Status. Click Update to confirm.
Limit the number of Issues loaded	Issues load under the Filter field; edit the limit attribute in issueconfig.json to set the maximum displayed — see "User Properties."
Export attributes/custom properties from the Details tab	More Actions dropdown → Export as CSV icon (use Batch Edit to export multiple). Downloads issues.csv to your browser's Downloads folder; multiple Issues appear as separate rows.
Change the release level	Details tab → Status dropdown → select the level (available levels determined by transitions defined in Capital Project Manager) → click Update. See also "Release Levels" in "Issues Overview."
Edit the Properties tab	See "Using Properties."
Edit the Comments tab	See "Using Comments."