auto-pull in SalesForce to populate mapped fields

  • 1
  • Question
  • Updated 1 year ago
Hello Connector for Salesforce.com & JIRA community, 

We've implemented the Connector for Salesforce.com & JIRA Cloud solution, and have an issue. 
After associating a Jira issue from within the SalesForce case, having 2 SalesForce fields mapped to receive Jira information, doesn't get populate after the association (despite the default connection being set to 'auto-push'):



The fields in SalesForce gets the information after manually 'Pull', and a refresh of the SalesForce case:  



Is there anyway to make this automated? (without the need to hit 'Pull').


Thanks for the assistance. 
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 1
Photo of Aidin Mahmoodi

Aidin Mahmoodi, Alum

  • 267 Posts
  • 6 Reply Likes
Hi Ido,

We have a post-function on JIRA side that you can configure on your Project Workflows.

You can follow this documentation, however make sure that you select the Push to Salesforce post function and not the Create Salesforce Object.

Here is a screenshot:



Cheers,
Aidin
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Hi Aidin, 

Any chance you can further assist in achieving a 'pull' on initial Jira association? This will greatly assist with our overhaul automation, as currently we are 'pulling' manually for each issue associated. 

Thank you for the ongoing assistance. 
Ido. 
Photo of Aidin Mahmoodi

Aidin Mahmoodi, Alum

  • 267 Posts
  • 6 Reply Likes
Hi Ido,

Sorry for the delay.

The workaround that I have suggested is only applicable if you are creating new JIRA issues from Salesforce side. basically it triggers upon Create function and not Associate.

Cheers,
Aidin
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Thank you for your reply. 

Perhaps you could raise this as a new feature request - ask I believe the use case is quite common (auto 'pull' after initial Jira association within SalesForce, to populate all the mapped fields accordingly). 

Thanks for the support here. 
Ido. 
Photo of Aidin Mahmoodi

Aidin Mahmoodi, Alum

  • 267 Posts
  • 6 Reply Likes
Hi Ido,

Sure, I will raise a feature request on your behalf.

Cheers,
Aidin
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Hey Aidin, 

Just quickly checking back if you have any new information to be shared on the 'auto-pull' feature request, as our team is not in fully understanding that they need to manually 'pull' in SalesForce, after they associated the Jira issue. 

Thank you for your assistance,
Ido.
Photo of Kevin Lew

Kevin Lew, Official Rep

  • 50 Posts
  • 2 Reply Likes
Hi Ido,

We already have an improvement request to this "auto-pull" feature on Salesforce side and have up-voted it on your behalf. However, the probability depends on feasibility and market demands.

Cheers,
Kevin
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Thanks for the update Kevin. 

Please let me know if there is anything we can do to assist in pushing this request in SalesForce (perhaps up-vote and existing Idea / Known Issue?). 
Photo of Doug Maskill

Doug Maskill

  • 11 Posts
  • 1 Reply Like
Any update on this, really needing the Jira "Updated" Field(last date/time the Jira Issue was modified) to auto update a corresponding custom field in Salesforce so we can trigger Salesforce notifications anytime a comment from Dev is added to an associated Jira Issue.
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
I recently discovered that the latest version include the much anticipated supplement. When associating a Jira issue, one can chose to 'pull from Jira', which is exactly what we needed, to avoid our Support Agent having to click 'pull' after association (they always forget): 



Thank you very much for adding this small feature. 
Photo of Adrien Low

Adrien Low, Alum

  • 85 Posts
  • 3 Reply Likes
Hello Ido,
When using 'create JIRA issue', add the 'After associating' selection, so we could have auto-pull in together with the issue creation, without the need to 'manually' Pull afterwards. 
Do you mean that you would like the newly created JIRA Issue to auto-push to Salesforce after clicking on the Create JIRA Issue button in Salesforce?

If that is the case, perhaps you can try the post-function that is available to be configured in JIRA.

The post function will auto-push from JIRA to Salesforce after the creation of the JIRA Issue.

Regards,
Adrien
(Edited)
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Thanks Adrien. 

As far as I understand the 'post-function', it will create a new SalesForce case, which is different then what we'd like to achieve (create a Jira issue from the existing SalesForce case). 

Can you confirm my understanding that Post Function creates a new SF case? 
Photo of Adrien Low

Adrien Low, Alum

  • 85 Posts
  • 3 Reply Likes
Hello Ido,

There are currently two post-functions that are available in the Cloud Connector.

The Create Salesforce Object post-function which will automatically create a new Salesforce Case after the creation of the JIRA Issue as you mentioned.

The other post-function, Push to Salesforce, will auto-push all mapped values to associated Case objects after the creation of the JIRA Issue. This post-function will not create a new Case Object.

The documentation that was provided previously contains both of the above mentioned post-functions.

Regards,
Adrien
(Edited)
Photo of Ido Greenbaum

Ido Greenbaum

  • 42 Posts
  • 2 Reply Likes
Thanks Adrien. 
We configured Post Function and SalesForce fields are auto populated when 'create a Jira issue' is done in SalesForce. 

Thanks for the assistance. 
Photo of Adrien Low

Adrien Low, Alum

  • 85 Posts
  • 3 Reply Likes
Hello Ido,

Glad to be able to help.

Regards,
Adrien
Photo of Doug Maskill

Doug Maskill

  • 11 Posts
  • 1 Reply Like
Does the latest version allow the following automation? Needing the Jira "Updated" Field(last date/time the Jira Issue was modified) to auto update a corresponding custom field in Salesforce so we can trigger Salesforce notifications anytime a comment from Dev is added to an associated Jira Issue.
Photo of Adrien Low

Adrien Low, Alum

  • 85 Posts
  • 3 Reply Likes
Hello Doug,

The latest version of the Cloud Connector now allows the Updated field to auto-push to mapped Salesforce's field.

Please refer to our released notes for more information on released features and bug fixes.

Regards,
Adrien
Photo of Doug Maskill

Doug Maskill

  • 11 Posts
  • 1 Reply Like
Is there any risk in Updating from 1.0.7-AC to 1.1.4-AC ?
Will I have to reconfigure or will I lose my connections or mapping?
Currently if I select Mapping it won’t even display the mapping but it still seems to work ok and syncing between Salesforce and Jira. After updating in Jira does anything need to be done in Salesforce?
Please advise
Photo of Kevin Lew

Kevin Lew, Official Rep

  • 50 Posts
  • 2 Reply Likes
Hello Doug,

For Salesforce & JIRA Cloud connector, it should be automatically update to the latest version. 

Can you please provide us with a screenshot of your Connector for further review?
  • Go to JIRA -> Add-ons -> Manage Add-ons -> Expand Salesforce & JIRA Cloud Connector section-> Full Screenshot
Regards,
Kevin
Photo of Doug Maskill

Doug Maskill

  • 11 Posts
  • 1 Reply Like
Looks like I would need to select "Update" , doesn't look automatic.
Photo of Kevin Lew

Kevin Lew, Official Rep

  • 50 Posts
  • 2 Reply Likes
Hello Doug,

There are several reasons that may cause your add-on to not update automatically. Please refer to this link for more information.

However, we highly recommend that you update your Salesforce & JIRA Cloud Connector to the latest version. There should be no problem after the update is performed.

Regards,
Kevin