Integrations Group — JHamilton129815 (Community Member) asked a question.
Why aren't Jira custom fields showing in the Field Mappings add-in configuration Jira drop down?
I installed the Veracode plugin in Jira Server 7.1.1. The integration works really well! However, I want to configure mapping from Veracode Common/Static fields to Jira custom fields. The integration guide states this can be done, yet when going to the "Field Mappings" menu item in the add-in configuration and dropping down the Jira fields list, none of my custom fields are showing. I created new custom fields in Jira that are of type Text Field (single line) and they successfully show up on the issue type screen. How does the plugin look for custom fields to populate in the Jira custom fields dropdown box?
.png){kind=logo}
Hi @JHamilton129815 (Community Member) , have you provided the Jira credentials to the plugin? See the Help Center.
Hi @Tim J (Veracode PM) (Veracode), if you are referring to setting the "Jira User" on the "Findings Import" page in the add-in > Veracode Configuration section, then yes this has been set to an admin user. Note that the import is actually working well. Just looking for the Veracode > Jira custom field mappings. Is there another area in which to set the Jira user?
Hi @JHamilton129815 (Community Member),
If the Jira fields drop down is empty, then likely an error happened when our plugin retrieves the list of all custom fields from Jira. The atlassian-jira.log (in directory <jira_home>/Application Data/JIRA/log) should contain an error message to indicate the cause.
If the Jira fields drop down is not empty, then it could be either:
1) the custom field name is one of the following name that our plugin excludes (since they're deemed non-mappable):
Rank,
Story Points,
Mitigation Status and Comments,
Veracode Link,
Epic Status,
Epic Colour,
Epic Color,
Summary,
Testing status,
Test sessions,
Sprint,
Development,
Votes,
Capture for JIRA URL,
Capture for JIRA browser,
Capture for JIRA jQuery version,
Capture for JIRA operating system,
Capture for JIRA screen resolution,
Capture for JIRA user agent,
Raised during
or 2) the Java class representing the custom field is not the one that's expected. If this is the suspected cause, then a support case would be needed for a deeper investigation.
Hope this is clear and helpful
Thanks @Kin (Community Member). I identified that it's calling loadJiraFields.jspa which returns only these:
{"jiraAllFields": ["Affects Version/s",
"Assignee",
"Component/s",
"Description",
"Description (overwrite)",
"Due Date",
"Environment",
"Fix Version/s",
"Issue Type",
"Labels",
"Original Estimate",
"Reporter",
"Time Spent"
]
}
The field type is com.atlassian.jira.plugin.system.customfieldtypes:textfield.
I'll submit a ticket. I found nothing in the logs with respect to errors or other useful info.