Jira field is not available in the integration mappings

A common question we receive about the Jira integration is, "Why is _____ field not available to be mapped in the Jira integration?"

The answer almost always is that the field we are supposed to send the data to is not visible on the correct Screens in Jira. 

Screens in Jira define what fields are available when creating, editing or viewing a feature. Each of those actions can have a different Screen assigned and therefore a field can be visible when viewing a feature but not actually be visible when creating or editing the feature.

This causes a problem and a lot of confusion because Aha! needs the field visible on create and edit to communicate through the API and the user assumes it is visible because they can see the field when they view the issue.

To fix this, you will need to complete a few steps in both Aha! and Jira. 

Note: In April 2019 Jira updated their product layout. If this change affects you, or you have trouble resolving your Jira integration issue, please contact our team of product management experts at support@aha.io

In Jira

1. Log in as the same user you used to configure the Aha! > Jira integration. Go to Settings > Projects > [Your project] > Screens

This will let you know what Screens in Jira are being used for the three operations of a project (Create Issue, Edit Issue, View Issue). Note which screens are being used for both Edit Issue and Create IssueEdit Issue and Create Issue are the operations Aha! uses to update objects in Jira via the Jira API. 

2. Edit the screens used by both Edit Issue and Create Issue so the correct fields are visible. Go to Settings > Issues > Field Configurations > Configure.

3. Find the field you want (Ctrl+F / CMD+F to search whatever field was displayed as part of your error message). You will see a list of all screens that contain that field. Click the Screens link to the right of that list.

4. You will see a list of screens with a Select checkbox next to each. Tick the checkbox for the screen(s) that is used by Edit Issue and Create Issue.  

5. Click Update.

6. Click Create (button at the top) and create a new issue (e.g.: User Story). Verify that the field you edited is now visible in your issue create workflow.

In Aha!

The last step is to update Aha! with the newly available field.

1. In Aha!, go to Settings > Product and select your Jira integration.

2. Click Load project data to force Aha! to update available fields.

3. Open the Mappings tab and the field should now appear.

4. Try sending a feature or release. The data that was previously not showing up should be there!

Was this article helpful?
0 out of 0 found this helpful