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

Why is a new baseline created for a Component that the GUI says has no changes (no asterisk)?


I am using RTC 6.0.6.1.

I created a baseline for a child component. And then, I took the snapshot for the stream which contains that components. But, in this scenario the parent child gets a new baseline.

For an example, Let's assume a stream consist of component named 'A' which has subcomponent named 'ABC' which in turn has another sub component named 'DEF'(i.e.,Component is A, A is having component 'ABC', 'ABC' is having component 'DEF'). Now, I created a baseline for subcomponent 'DEF' (after undergoing some changes and delivering them). I don’t see star mark on any of these 3 hierarchical components à all are baselined. And I have not selected “Create new baselines even for unchanged components” while creating snapshot.

 Then I took a snapshot for a stream. I could able to observe that the 'A' and 'ABC' is getting new baseline name which is similar to the snapshot name by replacing the existing baseline.

Why does this happen even though there is no change observed ?  Is it the expected behavior ?



0 votes


Accepted answer

Permanent link
This is now implemented as part of 703 M6 published on jazz.net
It is listed on the New & Noteworthy page

Rosa Naranjo selected this answer as the correct answer

0 votes


One other answer

Permanent link

The system is correctly creating a new baseline, but the defect here is that the GUI is not showing you (via an asterisk) that there are changes to that component. I have filed defect https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/493314 to get this fixed.


In particular, the problem is that the asterisk is only set if the component itself has some un-baselined change sets, but it should also be set if any of the child components of that component have either a new baseline or un-baselined change sets.   So I believe it should be the case (as you expected) that if there is no asterisk on a component, then a "make-baseline" on that component should not create new baselines.

0 votes

Comments
Hi Geoff,
This behavior I have even observed in 6.0.6 and before.
Let me know in which version I can expect a fix for this ?

Thanks,
Rakesh A

If you add yourself as a subscriber to that Defect, you will get email whenever any action is taken.  In particular, if you look at the "planned-for" date of the work item, you will see that it is scheduled to be fixed in the first sprint of 7.0.1.  The next release (7.0) is no longer in development (only stop stop-ship bugs will be fixed in 7.0).   

Your answer

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

Question asked: Oct 21 '19, 6:32 a.m.

Question was seen: 1,752 times

Last updated: May 02 '22, 4:25 p.m.

Confirmation Cancel Confirm