Integration with Other Applications > Integrated Software Management > Software Defect Tracking Integrations > Adapters Administration Utility Access for Managers and Users > Adapters Configuration Management for Users > Adapters Administration Utility > Working with Integrity Defects, Bugzilla, and Atlassian JIRA Adapters > Managing Context Associations
  
Managing Context Associations
DTS Adapters have "explicit" context associations. Context is the generic name for the container to which objects belong. An explicit association always refers 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. Integrity Defects, Bugzilla and Atlassian JIRA adapters have Product, Project, or Library context associations.
Context associations to adapters are listed in:
The Adapter Associations table.
The
Associations tab in the Defect Tracking System - <adapter name> information page.
Administrators can determine the adapter content that can be viewed through the Windchill associated context. This content can be a mainline, variant, or build project.
Integrity Defects, Bugzilla and Atlassian JIRA adapters can have one or more context associations to an adapter. A mapping file is also required for each adapter context association. Once the mapping file is defined, it will be applied for any existing and future context associations.
* 
Mapping files are managed by your Site or Organization administrator.