Prevent the changing of a group's/project's path from affecting pipeline execution policies with paths in them

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Why are we doing this work

• pipeline execution policies have the actual group/project path in them instead of the group's/project's ids like the policy scope feature
• group/project paths can be changed by admins, owners, and maintainers (docs 1, 2, 3), rendering the policy inactive
• group/project ids cannot be changed

Relevant links

For more information, see this thread

Non-functional requirements

• Documentation:
• Feature flag:
• Performance:
• Testing:

Implementation plan

Verification steps