Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

What is the intended purpose of the limit by lifecycle query attribute in DNG, and how is it meant to support link-based filtering

In DNG, there is a requirement to filter artifacts based on:

  • "Validated By" links (Typically to test artifacts)
  • "Satisfied by architecture element" links (Typically to affected items or rhapsody links)
  • However, DNG does not provide a direct filter attribute for link types such as validated by or satisfied by architecture element in the standard filter dialog
During analysis, the attribute "Limit by lifecycle query" was identified as a possible workaround. When applied:
  • Validated by filtering becomes possible by selecting Test items -> Status = All
  • Satisfied by architecture element filtering becomes possible by selecting affected items -> Status = All
While this workaround produces the expected results, the reasoning behind why this attribute enables such filtering is not well understood.

Questions:
  1. What is the intended design purpose of the "Limit by lifecycle query" attribute in DNG?
  2. Does the usage of "Status = All" a supported and recommended way to filter by the Prescence of the links?
  3. Are there any alternative or cleaner approaches to filter the links "Validated by" or "Satisfied by architecture element"?

0 votes


Be the first one to answer this question!

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 6,177

Question asked: May 14, 4:03 a.m.

Question was seen: 95 times

Last updated: May 14, 4:03 a.m.

Confirmation Cancel Confirm