Actually, all you need to do if you want a task to contribute to the relevance of the baseline is check the ‘Baseline will be relevant on applicable computers where this component is relevant’ box in the components tab of the edit baseline dialog. You have to click the expand icon next to the component name to see the box. The default for Fixlets is to have the box checked, and the default for tasks is to have the box unchecked.
This one is a good reminder for everyone with tasks within baselines. I bet there are lot of people out there with the relevance on the tasks not contributing to the relevance of the baseline and therefore are not triggering applicability.
rdamours is right. This baseline component relevance behavior is giving us a lot of confusion. Is it behavior by design or a bug?
Can someone give an example why would someone want to add a task in a baseline with the checkbox “Baseline will be relevant on applicable computers where this component is relevant” unchecked?
If this is by design, can you please make this option more visible for the added tasks (maybe expanded default view for tasks) or make the option available in collapsed view (under go to source link)
Actually this is a very common scenario. Many Tasks have a relevance of “true” (some settings Tasks, common configurations, custom restart tasks, etc). We saw that many people were including these Tasks in their baselines and got very confused when the baselines never went unrelevant.
I think we can try to make the option more prominent and I will send this suggestion to our UI designers for review.