Интеграция с другими приложениями > Интегрированное управление программным обеспечением > Software Defect Tracking Integrations > Adapters Management for Site and Organization Administrators > Adapters Administration Utility > Working with Integrity Defects, Bugzilla, and Atlassian JIRA Adapters > Managing Context Associations and Mapping Files
  
Managing Context Associations and Mapping Files
Integrity Defects, Bugzilla and Atlassian JIRA adapters can have one or more context associations to an adapter. Valid context associations are products, projects, and libraries.
Adapters have "explicit" context associations. Context is the generic name for the container to which objects belong. Explicit associations always refer to a context. Windchill supports the following types of contexts. (1) Site (a single one for the installation), (2) Organization, (3) Product, (4) Project and (5) Library. There is a "containment" relationship between contexts. The Site context comprises all Organizations that contain Products, Projects, and Libraries. Valid context associations are Products, Projects, and Libraries.
Context associations to adapters are listed in:
The Adapter Associations table.
The
Associations tab in the Defect Tracking System - <adapter name> information page.
A mapping file is required for each adapter. Once the mapping file is defined, it will be applied for any existing and future context associations. The mapping file for a context association to an adapter is listed in the Adapter Associations window.
For more information, see the following topics:
Creating or Editing a Mapping File
Selecting a Mapping File for an Adapter
Validating a Mapping File for an Adapter
Associating a Context and Selecting a Mapping File for an Adapter
Disassociating a Context from an Adapter