I want to manage release through Jira integrated with Github

[Ashmita Mishra]

1. There are more stories in a sprint

2. I have created version in Jira and linked those version as 'Fix version' to specific issue types

3. I have Github already integrated to Jira

I want to deploy all those issue types from Jira only when I release the specific version, and I want to see the release note

Please help on the same

[Javier Pozuelo -Exalate-]

Hi @Ashmita Mishra I'm the Community Manager at Exalate.

This is a great use case, and one we often see when teams want tighter control over deployments tied to Jira versions and GitHub commits.

Here’s how you can approach it:

• Since you’ve already linked GitHub with Jira and assigned Fix Versions to issues, you’re halfway there.

• To deploy only the issues assigned to a specific version, you'll need to ensure your CI/CD pipeline is version-aware, meaning it only picks commits linked to Jira issues with that Fix Version.

• This typically requires tagging or filtering commits or PRs in GitHub based on the Jira version metadata (can be scripted or done via deployment tools like Jenkins, GitHub Actions, or others).

• For release notes, Jira can generate them automatically using the version and associated issues, or you can customize them with tools like Advanced Roadmaps, Automation for Jira, or Marketplace apps designed for release management.

If you’re syncing Jira issues across tools (e.g., GitHub Issues, another Jira instance, ServiceNow, etc.), that’s where Exalate can help. It supports custom sync rules and automated workflows, keeping your data consistent across platforms.

Good luck with the integration!

[Hari Krishna]

Hi @Ashmita Mishra 

Yes, this is possible with Jira and GitHub integration. Here's how you can achieve it:

1. First, tag all the issues with a Fix Version (example: v1.0.0)

2. Then, go to Jira → Releases → Create the version (v1.0.0) → Release it when ready

3. Now set up an Automation rule:

• Trigger: Version Released

• Action: Send Web Request (Webhook to GitHub or your CI/CD tool)

• Include version name (v1.0.0) in the payload

4. In GitHub, create a GitHub Action that listens to the webhook and triggers deployment for that version

5. After releasing, go to Jira → Releases → v1.0.0 → You’ll see the auto-generated Release Notes with all linked issues

So once the version is released in Jira, your GitHub deployment kicks off, and Jira handles the release notes for you