It's all about the answers!

Ask a question

What other factors besides work items planned for omit iterations in various report parameters ?

Kevin Ramer (4.5k6172190) | asked Oct 20 '15, 4:09 p.m.
Like user is questioning why a particular iteration does not show the associated child iterations in the Advanced Release Burndown ( "modern" version ) when a time line is chosen.  Another similar time line/iteration shows the child iterations

I have tried to compare the two time scenario and don't see any differences.   The ABD says the last snapshot was Oct 18, 2015 ~16:00.  Looking at the DCC jobs the nearest in time is the Work Items Snapshot, which has run also on 19th.

RTC 5.0.2 ifix006.

Suggestions welcome.

3 answers

permanent link
Rafik Jaouani (5.0k16) | answered Oct 22 '15, 11:13 a.m.
Iteration must have some work items associated with it. That should be it.

Kevin Ramer commented Oct 22 '15, 11:19 a.m.

What about having only a few ( 5 or so ) child iterations ?  

permanent link
Kevin Ramer (4.5k6172190) | answered Oct 23 '15, 2:45 p.m.
FWIW:  Quering the info about the resource I get:

  • <>
  • <id>workitems.AdvancedReleaseBurndown</id>
  • <modified>2015-03-21T16:01:52.174-0400</modified>
  • <modifiedBy>
  • <name>ADMIN</name>
  • </modifiedBy>
  • <projectArea>
  • <name>BSM</name>
  • </projectArea>
  • <contents>
  • <key></key>
  • <value>
  • </value>
  • </contents>
  • </>
  • All the other projects ( at least on the 1st page ) have a similar timestamp.

    permanent link
    Rafik Jaouani (5.0k16) | answered Oct 23 '15, 4:14 p.m.
    Turns out RTC and DCC were using two different data warehouses. The same data warehouse must be shared among  all CLM apps, the JTS and DCC.

    Your answer

    Register or to post your answer.