Tracking change-sets in a work-item across streams
![]()
Is there a proper way to track and display clearly to which streams the change-sets associated to a work item were flowed?
Right now, if we have merges or patches applied that are in excess to the original change-sets we do duplicate the work-item and indicate and append to its summary the stream name to which those changes were flowed. What should we do if there are no additional change-sets and we want to track that the changes in this workitem were flowed to those streams (without having to manually go through the change-sets)? AND is there a solution that is independent of streams changing names? |
4 answers
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 18 '09, 8:59 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The "history" of each component in a stream (or for that matter, a
workspace), lists all of the change sets that have flowed into that stream. This history is not affected by changing the name of the stream. Cheers, Geoff hyassine wrote: Is there a proper way to track and display clearly to which streams |
![]()
Thanks for your reply...
I am aware of a few methods for checking whether or not a change-set has been flowed to a stream or not, but I am looking for something that makes it stand out in a work-item. In other words I want something to answer the more general question of: "To which streams has this change-set been flowed?" (the answer would be a full list of streams) rather than the more specific question: "Has this change-set been flowed to this stream..." I realize that by simply accepting a change-set in a repository workspace, it will display an error message saying that the change-set has already been flowed before, but I'm wondering if there is something more tailored to what I described above. (I can't rely on build tags since some of our streams are not continuously built) The "history" of each component in a stream (or for that matter, a Is there a proper way to track and display clearly to which streams |
![]()
Haytham,
Yep this one is high on our list for 3.0, we have an item to track it already: 93619: Track where changes have been delivered Cheers, Jean-Michel |
![]()
Thanks for the feedback Jean-Michel, we'll wait for 3.0 for this feature then!
Cheers, Haytham Haytham, |
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.