Helper text for pipeline execution policy configuration

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

• Close this issue

Release notes

Problem to solve

As a follow-up UX improvement from the functional fix in Job with custom stage not included in pipeline ... (#494431 - closed), we want to explore how to provide more clarity/guidance to users in the UI for configuration of pipeline execution policies.

Example use cases:

• When migrating from compliance pipelines, understanding the impact of using project:include.
• When choosing inject vs override, understanding the different impacts or inputs required.

Intended users

User experience goal

Proposal

Proposed Fixes/Improvements

1. Provide guidance to users in the UI to ensure they understand the impact of their configuration for the pipeline execution policy, including the behavior to expect when using project:include.

Current	Proposed

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references