Trying to find out the real use case of having Associated rules in Feature.
As I understand when a rule is checked IN, the developer will have the option to associate the rule to the User story but the rule is ideally associated with the feature rather than the user story.
With this I can conclude the following
1) A feature can end up having bunch of rules associated with it.
2) If a rule is shared across other functionality then upon checkin of the rule, the rule will be associated with multiple features or to the latest associated feature.
So the whole idea is to package the code and requirement but cant understand how effective it is for the project? How is this valuable to the customer and the implementation team? Why not the rule to be associated with a User story than to have at feature level?
If a user story is mapped to a feature, a rule check-in will internally maintain link between the user story and rule. This can be seen from the View XML of a rule that is checked in against a user story. As features become the central repository of all the artifacts, the associated rules are currently shown under it.