How to create development status after pr merged

[xyz]

Hello, I'm working on integrating GitHub Actions with Jira to generate Cycle Time Reports and have some questions regarding the implementation.

Our current development workflow is as follows:

After planning a new version, we immediately create a PR from release/1.0.x to main to consolidate all features for testing. We want the Jira development status to be triggered only when the release branch PR is merged into main, NOT upon PR creation or updates.

However, in testing the following workflow configuration, the development status isn't being properly created after code merging. Could you advise on how to resolve this?

when I use pull_request trigger, all things work fine

[Humashankar VJ]

Hi @xyz 

Jira Cloud’s development status is provided by the native GitHub–Jira integration, which includes Jira’s “development information” (e.g., pull requests, commits). This status is not directly controlled by custom workflow logic in GitHub Actions.

To ensure that the development status only reflects PRs merged from release/1.0.x to main, you'll need to leverage the way the Jira–GitHub app processes pull requests. To enhance, you can use Jira Automation to further refine how and when development statuses are updated based on the merged PRs.

Hope this helps !!