When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira
I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check that the values are populated in the originating system and that the mappings are correct, then try again.
I am unable to map Aha! data to the FixVersion field in Jira, but can map FixVersion from Jira to Aha! Therefore, the Epic cannot be created in Jira as FixVersion is required and set as Autocomplete Renderer - with a drop down list. Aha! should have a way of handling this type of field
-
ADMIN RESPONSEAug 24, 2018
Thank you for your idea. This is currently possible. If you have not already added a Release -> Fix Version record mapping you will need to do so. This is a default record mapping, so it is likely that it is already set. You can then add the Release -> Fix version Links to mapping for features and master features. This will set the fix version when the new issues are created in Jira.
This article explains the links to mappings in more detail.
© 2025 Aha! Labs Inc.•All rights reserved
Thanks Austin for coming back on this. So it seems that you are saying that if I would first added the record mapping of Release -> Fix version - that would fix this issue. However there is no "Release" option in the drop-down list as per the attached. Any thoughts on why this is happening?
Hi there, I have discussed this in more detail with our customer success team. The reason you are not seeing the option to add the Release -> Fix version links to mapping is because you would first need to add the record mapping of Release -> Fix version.
This would solve the issue and would allow you to send new features from Aha! to Jira even with the required fix version field. However, I understand that this may not be an option for your particular use case.
At this time, we are unlikely to implement a change to allow a custom field in Aha! to map from Aha! to the Jira fix version field. One option for working around this would be to change the fix version field for this Jira project to not be required.
I have asked our customer success team to connect as well so that we can provide more guidance directly rather than on the portal. Thank you!
Hi Austin, was hoping you could share how the above was resolved? There is no option to add Release --> Fix version mapping against "Links to:" under Feature --> User story record mapping so wondering what is the proposed workaround here.
hi, based on the response that record mapping from Release -> Fix Version is possible, I have the following questions:
1) How does Aha! expect Fix Version is configured in Jira? (technically: required, drop down list, etc)
2) How does Aha! expect customers to use Fix Version compared to Release? In our case, we have weekly Fix Versions.
thanks
Gale
Hi there. Someone from our customer success team will be in touch to help you out. Thanks!
here is a screen shot
Also, when I select on Links at the top of the page - as per your article, I don't have any options to choose from
Unfortunately this doesn't appear as an option in my project. First, in the Aha! mapping, fixversion (for Jira) will not allow me to map an Aha! field to it. I can only map fixversion to an Aha! field. Second, the field Release does not appear in the field selection when I have selected fixversion on the Jira side. Lastly, we use FixVersion for weekly releases we have so it wouldn't map well to Releases in aha!