As the Flow progresses, the promotion mechanism:

* Retrieves the promotion contextfrom the previous hook

* Passes the context automatically to the next hook as input parameters:

* New parameters are added tothe input parameters of the next hook

* For existing parameters, the value ofthe parameter inthe current hook always takes precedence

* Retrieves the promotion contextexported by the previous hook

* Passes thepromotioncontext automatically to the next hook

* If the current hook defines one or more oftheparameters from the promotion context asinput parameters, their values are taken from the context

* If the current hook also exports a promotion context withthesameparameter, the value fromthe current hook’s promotion context overrides the value from the previous context

| --------------| --------------|

|**Two-step DAG structure**| The hook uses a Directed Acyclic Graph (DAG) with two tasks: first`create-issue`, then`set-promotion-context`. The second task depends on the successful creation of the Jira issue.|

|**Jira issue creation**| The`create-issue` task uses a custom container to create a Jira ticket.|

|**Promotion context definition**| After theissue is created, the`set-promotion-context` task creates a JSON object with the full Jira issue URL. This JSON is saved to`/tmp/promotion-context.txt` and exported as the`PROMOTION_CONTEXT` global output.|

|**Sharing information across hooks**| By exporting`PROMOTION_CONTEXT`, later hooks in the same Promotion Flow,like a Slack notification hook, canaccess the Jira issue details.|

|**Promotion context definition**| AftercreatingtheJira issue, the`set-promotion-context` task creates a JSON object with the full Jira issue URL. This JSON is saved to`/tmp/promotion-context.txt` and exported as the`PROMOTION_CONTEXT` global output.|

|**Sharing information across hooks**| By exporting`PROMOTION_CONTEXT`, later hooks in the same Promotion Flow,haveaccess to the Jira issue details.|