Following is the standard mapping used to determine what Jira Version Field to use, to a resolve a Global Configuration, depending on
the OSLC Link Type (Change Management) or the OSLC Resource Type (Quality Management). This mapping can be seen (and customized) by
clicking the viewed here link on the top of the Global Configurations page (once Configuration Management has been enabled).
Note: only the resource types mapped in the Issue Type Mapping page will be listed in the dialog.
| Target Domain | OSLC Link Type | Jira Version Field |
|---|---|---|
| Architecture Management | elaborated by architecture element | Affects Version/s |
| Change Management | affected by defect | N/A |
| affects plan item | N/A | |
| contributes to | N/A | |
| related change request | N/A | |
| tracks | N/A | |
| Requirements Management | affects requirement | Affects Version/s |
| implements requirement | Fix Version/s | |
| tracks requirement | Fix Version/s | |
| Quality Management | affects test case result | Affects Version/s |
| blocks test execution | Affects Version/s | |
| related test case | Affects Version/s | |
| related test execution record | Affects Version/s | |
| related test plan | Affects Version/s | |
| related test script | Affects Version/s | |
| tested by test case | Fix Version/s |
| OSLC Resource Type | Jira Version Field |
|---|---|
| Test Case | Fix Version/s |
| Test Plan | Affects Version/s |
| Test Execution Record | Affects Version/s |
| Test Result | Affects Version/s |
| Test Script | Fix Version/s |
To customize the standard configuration click on the Customize button, change the configuration as required, and click the Save button.
Note: making changes may affect all existing Collaboration Links, breaking some of them or worst, making them point to a different version of an artifact.