Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Salesforce Connector not able to map to JIRA Summary field

Nicholas Zozaya March 21, 2020

I'm configuring ServiceRocket Salesforce <> JIRA connector. The integration is setup correctly, I can manually create a JIRA Issue from Salesforce, however, when attempting to automatically create a JIRA issue I get an error about Summary not being populated: 

JIRA validation failed! summary: You must specify a summary of the issue.

After confirming that my mappings were setup correctly, I read that this probably has to do with the Summary field not being on the Screen for the project/issue type. I've confirmed that the summary is present on the creation page for this project/issue type, and have attached a screenshot of same.

Screen Shot 2020-03-21 at 10.14.24 AM.png

Here's a screenshot of my field mappings (bindings):

Screen Shot 2020-03-21 at 10.18.44 AM.png

So, I'd like to understand alternative reasons why the JIRA summary field wouldn't be populating from Salesforce.

3 answers

1 accepted

0 votes
Answer accepted
Nicholas Zozaya March 21, 2020

I incorrectly bound the project to a Salesforce Production url instead of the Sandbox url (where I was attempting to automatically create Issues from). Once I deleted the existing connection, then recreated a new one which linked to the Sandbox environment, all of the mapping issues were fixed.

0 votes
Yamam Al Ghourani_ServiceRocket_
Contributor
March 23, 2020

Hi Nicholas, 

This is Yamam from ServiceRocket support team, and I wanted to make sure all of your questions are answered. 

JIRA validation failed! summary: You must specify a summary of the issue.

When auto-creating Jira issues you'll need to make sure that all Jira mandatory fields have some value so that the Jira issue gets created. This can be resolved by mapping a salesforce field to the Summary Jira field (Jira Icon > Salesforce > Bindings > Mapping > Mappings ).

It seems that you were able to resolve the issue which was due to binding the project to Production instead of Sandbox. If you had any questions or run into any issue in the future, you can reach out to via our support portal and chat channel: https://atlassian.servicerocket.com/ 

Nicholas Zozaya March 23, 2020

Thanks

0 votes
Nicholas Zozaya March 21, 2020

Update:

It seems that none of my connection bindings are working to map Opportunity fields to JIRA Issue fields. So I'm able to manually create an Issue from Salesforce UI and see it in JIRA, but the configured mappings shown in the second screenshot above are not working.

To confirm that my Project Connection object settings are configured correctly, here's a screenshot.

Screen Shot 2020-03-21 at 10.45.59 AM.png

Suggest an answer

Log in or Sign up to answer