feat: trigger Jira issue automation on PR merge event #11

andrey-canon · 2025-07-04T22:50:13Z

Description

This PR improves the GitHub Actions workflow responsible for creating Jira issues by:

Dynamically generating the story and sub-task information based on repository and pull request metadata.
Automatically assigning the appropriate deployment environment based on the target branch.

These changes enhance automation and reduce manual effort when tracking development work in Jira.

johanseto · 2025-07-07T20:29:49Z

.github/workflows/create-jira-issue.yml

+      story_summary: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_SUMMARY }}
+      story_description: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_DESCRIPTION }}
+    steps:
+      - run: echo "Preparing input vars..."


This doesnt print anything

that prints Preparing input vars...

johanseto · 2025-07-07T20:30:24Z

.github/workflows/create-jira-issue.yml

+      - synchronize  # Delete after testing and delete || github.event.action == 'synchronize'
+
+jobs:
+  prepare:


I think this job could be removed and set the inputs directly in the jira-issue job

That doesn't work since the create-jira-issue job requires environment variables and it's not possible to set any environment when the job implements a reusable workflow https://stackoverflow.com/questions/75386901/environments-in-github-actions-incompatible-with-reusable-workflows?utm_source=chatgpt.com

johanseto · 2025-07-07T20:30:53Z

.github/workflows/create-jira-issue.yml

+    if: github.event.pull_request.merged == true || github.event.action == 'synchronize'
+    uses: nelc/actions-hub/.github/workflows/create-jira-issue.yml@and/jira_automation_action
+    with:
+      story_summary: ${{ needs.prepare.outputs.story_summary }}


Suggested change

story_summary: ${{ needs.prepare.outputs.story_summary }}

story_summary: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_SUMMARY }}

This only works with repo variables, it's no possible to use environment variables

I think env.MIGRATION_BACKLOG_JIRA_STORY_SUMMARY doesnt work and vars yes. Or vars are not repo vars?. I mean here you could testing set env ${{ github.event.pull_request.base.ref }}.

https://docs.github.com/en/actions/reference/contexts-reference#contexts

#11 (comment)

https://github.com/nelc/brand-openedx/pull/11/files#r2191128073

johanseto · 2025-07-07T20:31:04Z

.github/workflows/create-jira-issue.yml

+    uses: nelc/actions-hub/.github/workflows/create-jira-issue.yml@and/jira_automation_action
+    with:
+      story_summary: ${{ needs.prepare.outputs.story_summary }}
+      story_description: ${{ needs.prepare.outputs.story_description }}


Suggested change

story_description: ${{ needs.prepare.outputs.story_description }}

story_description: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_DESCRIPTION }}

This only works with repo variables, it's no possible to use environment variables

johanseto · 2025-07-07T22:45:30Z

.github/workflows/create-jira-issue.yml

+      subtask_description: "${{ github.event.pull_request.body }} 🔗 PR: ${{ github.event.pull_request.html_url }}"
+      environment: ${{ github.event.pull_request.base.ref }}
+    secrets:
+      MIGRATION_BACKLOG_JIRA_EMAIL: ${{ secrets.MIGRATION_BACKLOG_JIRA_EMAIL }}


So, how are these secrets being resolved if they are environment secrets?

Why vars don’t work in with:

GitHub evaluates that expression at the caller workflow level, before the reusable workflow starts.

At that point:

The environment has not been set yet.

So environment-scoped vars are not available.

As a result, the value is undefined or empty.

secrets are always available and injected early by GitHub — even at the top level.

andrey-canon force-pushed the and/jira-automation-trigger-on-synchronize branch 2 times, most recently from d6299f1 to 7d143df Compare July 4, 2025 22:58

andrey-canon had a problem deploying to open-release/redwood.nelp July 4, 2025 22:58 — with GitHub Actions Failure

andrey-canon temporarily deployed to open-release/redwood.nelp July 4, 2025 23:04 — with GitHub Actions Inactive

andrey-canon force-pushed the and/jira-automation-trigger-on-synchronize branch from 7d143df to 35bf541 Compare July 7, 2025 14:30

andrey-canon had a problem deploying to open-release/redwood.nelp July 7, 2025 14:30 — with GitHub Actions Failure

andrey-canon force-pushed the and/jira-automation-trigger-on-synchronize branch from 7040518 to f83f302 Compare July 7, 2025 14:36

andrey-canon had a problem deploying to open-release/redwood.nelp July 7, 2025 14:36 — with GitHub Actions Failure

andrey-canon force-pushed the and/jira-automation-trigger-on-synchronize branch from f83f302 to 164a4a8 Compare July 7, 2025 14:49

andrey-canon temporarily deployed to open-release/redwood.nelp July 7, 2025 14:49 — with GitHub Actions Inactive

andrey-canon requested a review from johanseto July 7, 2025 14:50

feat: trigger Jira issue automation on PR merge event

c0fd40e

andrey-canon force-pushed the and/jira-automation-trigger-on-synchronize branch from 164a4a8 to c0fd40e Compare July 7, 2025 15:34

andrey-canon temporarily deployed to open-release/redwood.nelp July 7, 2025 15:34 — with GitHub Actions Inactive

johanseto reviewed Jul 7, 2025

View reviewed changes

andrey-canon requested a review from johanseto July 7, 2025 21:49

johanseto reviewed Jul 7, 2025

View reviewed changes

johanseto approved these changes Jul 8, 2025

View reviewed changes

andrey-canon temporarily deployed to open-release/redwood.nelp July 8, 2025 21:07 — with GitHub Actions Inactive

feat: remove debug lines

441217e

andrey-canon merged commit 1fb420e into open-release/redwood.nelp Jul 8, 2025
1 check passed

andrey-canon temporarily deployed to open-release/redwood.nelp July 8, 2025 21:25 — with GitHub Actions Inactive

andrey-canon had a problem deploying to open-release/redwood.nelp July 8, 2025 21:25 — with GitHub Actions Failure

andrey-canon had a problem deploying to open-release/redwood.nelp July 8, 2025 21:27 — with GitHub Actions Failure

andrey-canon temporarily deployed to open-release/redwood.nelp July 8, 2025 21:28 — with GitHub Actions Inactive

andrey-canon deployed to open-release/redwood.nelp July 8, 2025 21:28 — with GitHub Actions Active

andrey-canon mentioned this pull request Sep 30, 2025

feat: trigger Jira issue automation on PR merge event #12

Merged

	story_summary: ${{ needs.prepare.outputs.story_summary }}
	story_summary: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_SUMMARY }}

	story_description: ${{ needs.prepare.outputs.story_description }}
	story_description: ${{ vars.MIGRATION_BACKLOG_JIRA_STORY_DESCRIPTION }}

feat: trigger Jira issue automation on PR merge event #11

feat: trigger Jira issue automation on PR merge event #11

Uh oh!

Conversation

andrey-canon commented Jul 4, 2025

Description

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Why vars don’t work in with:

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants