Limitations of linking work items to versioned artifacts

This topic describes the limitations of linking work items to versioned artifacts that belong to configurations in Configuration Management-enabled project areas in applications such as Requirements Management and Quality Management.

The following limitations apply:

  • To navigate links to versioned artifacts, you must use the web client, the IBM® Engineering Workflow Management (EWM) client for Microsoft Visual Studio IDE, or the 6.0 (or greater) version of the EWM client for Eclipse IDE.
  • To create links to versioned artifacts, you must use the web client, the 6.0 (or greater) version of the EWM client for Eclipse IDE, or the 6.0 (or greater) version of the EWM client for Microsoft Visual Studio IDE.
  • In general, linking EWM plans to versioned artifacts is not supported. It is possible to create a link from a versioned artifact to a plan; however, when you navigate the link from within the plan, EWM uses the default configuration for the target project area. The default configuration might not be the same configuration from which the link to the plan was created.
  • If you have two or more releases associated with the same iteration and the same global configuration, establishing links from EWM to artifacts in other applications, such as Quality Management (QM) test plans, may result in duplicate links to the EWM artifact being displayed in the other application:Duplicate links in versioned artifacts
  • When you create a work item, you must select a value for the attribute that is mapped to the link type and save the work item before you can link to a versioned artifact.
  • In a work item that has links to versioned artifacts, if you change the value of the release (deliverable attribute type) field, the links are not updated until you save the work item.
  • You can link work items to versioned artifacts only if the configurations that contain those versioned artifacts belong to global configurations.
  • To specify the mapping of OSLC link types to attributes, and to associate releases with global configurations, you must use the web client.
  • While working in IBM Engineering Test Management or IBM Engineering Requirements Management DOORS® Next, you cannot create a link from a baseline to a work item. The workaround is to create the link from within the work item.
  • In the EWM client for Eclipse IDE, you can perform a bulk edit of work items to change the target link of versioned artifacts. If the selected work items belong to different releases and have different associated global configurations, EWM uses the target artifact versions that belong to the global configuration associated with the first work item in the selected collection.
  • In the web client plan editor, you can perform a bulk edit of work items to change the target link of versioned artifacts. If the selected work items belong to different releases and have different associated global configurations, EWM uses the target artifact versions that belong to the global configuration associated with the work item from which the context menu was activated.
  • The IBM Engineering Lifecycle Management includes a set of predefined lifecycle work item queries, which retrieve work items based on their links to artifacts in other applications, such as Requirements Management (RM) and Quality Management (QM). See Using lifecycle queries for the complete list of these queries. For work items that are linked to versioned RM and QM artifacts that do not belong to default configurations, the lifecycle query results might not be accurate.
  • Data warehouse reporting is not supported for links to versioned artifacts.
  • Any of the following actions can cause links from plans or work items to versioned artifacts to become invalid:
    • The association between the configuration and the global configuration changes.
    • The mappings specified on the Configuration Management > OSLC Link/Attribute Mapping page of the project area editor change.
    • The value of the work item attribute, such as Found In or Planned For, that is used to determine the global configuration changes.
    • The association between the release and the global configuration changes.
    • The association between the release and the iteration changes.
    • A user ignores the effective global configuration when creating a link from the Quality Management or Requirements Management project area.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki