Milestone Path Values need to be differentiated

[#1]

Description - When filtering on Milestone Path values, the current implementation shows all available values for all Paths. This creates confusion if 2 or more Milestone Paths define the same value. This can happen if there are different path values for different groups, with overlapping values. Since the Milestone Paths have a group selection to limit access, this same group selection should limit which path values are visible in filters.

Why is this feature important to you - Milestone Path access is controlled by groups, but the values visible to end users for filtering are not. This can create confusion if the same value exists across Milestone Path definitions.

How would you like the feature to work - Filtering on milestone ID or Milestone Name should be limited to the values in Milestone Paths the user has permission to see.

Current Behaviour - Milestone Id filter is not restricting which values show up, which can show multiple values with the same name with no differentiation or indicator of the path it is on.