Why is a new baseline created for a Component that the GUI says has no changes (no asterisk)?
![](http://jazz.net/_images/myphoto/b59b440e545a2735e4956b9147b1e52f.jpg)
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 ?
Accepted answer
![](http://jazz.net/_images/myphoto/b59b440e545a2735e4956b9147b1e52f.jpg)
One other answer
![](http://jazz.net/_images/myphoto/b59b440e545a2735e4956b9147b1e52f.jpg)
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.
Comments
![](http://jazz.net/_images/myphoto/196a7a681fa70ee2b591a2d394fda312.jpg)
![](http://jazz.net/_images/myphoto/a36d1dcfd3e1e1e00aeb18c860d1443d.jpg)
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).