Update Fix versions in tickets automatically when merging a PR

[Martin Cigorraga]

Hi all,

I’m trying to automate a step in our workflow and could use some help.

The problem:
Whenever we merge a PR that fixes a Jira issue, the Fix Versions field has to be updated manually for each ticket. This step is often forgotten, and it leads to inconsistent data in Jira.

What I want to do:
Have Jira automatically populate Fix Versions when a linked PR is merged in GitHub, based on predefined rules — the best option I found so far is using a label assigned to the PR. This also helps us enforce some repository rules to ensure that if the fix versions label is not set, the PR can't be merged.

What I want to do:
Have Jira automatically populate Fix Versions when a linked PR is merged in GitHub, based on predefined rules — for example: release branch name, tag, label, or a configured mapping.

Why:

• Removes the chance of human error

• Keeps Jira data accurate and consistent

• Saves time by eliminating repetitive manual work

I’ll share my current automation attempt below. Any guidance, examples, or pointers would be much appreciated.

Thanks in advance!

[Bill Sheboy]

Hi @Martin Cigorraga -- Welcome to the Atlassian Community!

This seems to be a duplicate of your question posted just a few minutes earlier.  Please consider closing this one (or ask the community managers to delete it) to help focus the suggestions.

Here is the earlier post, which already has suggestions:

https://community.atlassian.com/forums/Automation-questions/Update-Fix-versions-in-tickets-automatically-when-merging-a-PR/qaq-p/3090384

Thank you!

Kind regards,
Bill