Epic Goal

• We currently only allow a subset of custom variable (as well as customparams) for the user. This is nice and handle most use cases, but there is a lot in information in payload that may be interesting to use for users.

Why is this important?

• This would let users to achieve endless customization according to what the Git provider does.
• For example they could launch different tasks the labels on PR are different.
• We would be able to make it dynamic by making it a CEL expression and let the user do conditional as they wish in there

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment