When a planned shift is disrupted and replaced by a new one, not all disruptions are equally bad. A replacement shift that shares a relevant attribute with the original (such as the same location or department) is preferable to one that shares nothing.

Today, disruption rules can limit or reward based on time overlap with the original shift, but there is no way to reward a disruption based on shared tags between the original and the replacement shift.

The request is to allow configuring a disruption rule that rewards an employee when their replacement shift has a specific tag in common with the planned shift. This gives the solver a way to distinguish between a "less bad" disruption (same location, for example) and a fully unrelated one.