For anyone seeing this in 2025 I was able to accomplish this with an Automation. Post function hooks were not working for me on a create transition. I kept getting the error that the create original issue function needed to come first even when it did come first. Setting up an automation to set the fix version on issue create was straightforward enough.
Through JIRA configuration, you may create a post function on the Create transition of a given Issue Type that sets the Fix Version field, but you must specify a set value and it will apply everywhere for that Issue Type or at least Projects configured to utilize that issue type scheme.
If you do not wish to use the Fix Version field for whatever reason, you can remove the field from your configuration and screens. To be honest, I thought JIRA Core excluded this field by default...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I could not set a value to the fix version field since it does not appear as an option in the post function fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I can see it under "update field" when choosing a post function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, I am trying to find this option but I cannot see it available in "Update Issue Field" or "Update Issue Custom Field".
appreciate your comments and help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am trying to do the same thing and don't see the field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same for me. "Fix version" is not showing up in "Update Issue Field" (or "Update Issue Custom Field").
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This should not be the accepted answer, it is wrong. Yes, you can create a post function to update a select few fields but the 'fix version' field that was specifically asked about in this question is not one of the fields available to update.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Some apps allow to set field value, during a transition, using a post-fonction but Jira out of box does not offer this kind of features.
That's the reason I used another field and copy filed value during transition, Jira llows this using "Copy Value From Other Field".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
My response is probably coming late but I would like to share my workaround.
I simply created a custom field which is based on values provided in Version (Project Settings), I created a context for this field related to the project and there I was able to define a default value for this custom field. A the end I just copy value from this field to fixVersion field during issue creation transition. I used a plug-in workflow post function but it is may available in native Jira post-functions.
No code required and works fine!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also extremely late, but I don't understand why you would want a default on the fixversion. You don't know when it will be fixed.
I guess you would like to set a default 'affects version' being the latest released version
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Jira is no more only bug tracker for a long time. ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.