It's all about the answers!

Ask a question

DNG 6/7: reporting on non-delivered Change Sets?

Adrian Haw (2741241) | asked Jul 21 '22, 3:20 a.m.
I'm looking for a method to report a list of open (non-delivered) change sets.

In the perfect case a list per component for all components in a global configuration but a report for a single component at a time would also be ok.

I don't see how we can create such a report in Report Builder - does anyone have a different solution? Do we have to write a script and use private API calls?

Thanks for any feedback.

Accepted answer

permanent link
Ian Barnard (1.9k613) | answered Jul 22 '22, 3:10 a.m.
edited Jul 22 '22, 3:12 a.m.

Undelivered changesets in a stream are exposed in DN as a small supported extension of the CM API - although in 7.0.2 there was a defect which made all changesets visible this is resolved in one of the recent iFixes so just make sure you use the most recent (currently iFix014). I guess you'll have to write a script to get to these because they aren't put into the TRS for LQE - the API will return all undelivered changesets for a stream. See how to discover the configs in a component in my answer here (search for 'to details of all the configurations in the component' - although note the RDF there doesn't show undelivered changesets only because there weren't any in the stream I used as the example.

You will have to figure out the contributions using the GC API (for example see Jazz API Usage Scenario: Get a flat list of contributions for a GC hierarchy)

Adrian Haw selected this answer as the correct answer

One other answer

permanent link
David Honey (1.8k17) | answered Jul 21 '22, 5:08 a.m.
edited Jul 21 '22, 6:17 a.m.
I don't think that DOORS Next publishes change sets in its TRS. Reporting on change sets in JRS is not a supported use case.

Looking at examples of DOORS Next service provider catalogs (/rm/oslc_rm/catalog and /rm/oslc_config) I do not see any OSLC query capabilities for configurations or change sets. So there doesn't appear to be any OSLC defined way of querying for change sets.

I would highly recommend that you only use public APIs. The public APIs are documented at Private APIs are typically not documented, not supported for customer or 3rd party use, and may change without notice between releases. Implementations using them may find their use case are fragile over time, and not supportable.

Your answer

Register or 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.