I want to get my Saleforce Accounts on a Case into a Picklist Field in JIRA

General Questions
1

I have two options

  1. Account Name on a Case, default SFDC field
  2. A Custom Text Field that pulls the Account Name on a Case

My Goal is to take that Account Name and Send it to JIRA in a Picklist so that my Product and Engineering Team can report on Clients Impacted

My Salesforce Outgoing script is
replica.Jira_Account__c = entity.Jira_Account__c

My Current JIRA Incoming Script is
issue.customFields.“Client Impacted Test”?.value = nodeHelper.createOption(issue,“Client Impacted Test”, replica.customFields.“Jira_Account__c”?.value)

and I get the following error in JIRA
Cannot invoke “scala.collection.immutable.List.headOption()” because the return value of “jcloudnode.services.jcloud.hubobjects.NodeHelper.createOptions(com.exalate.api.domain.hubobject.v1_17.IHubIssue, java.lang.Long, scala.collection.immutable.List)” is null

the remote replica shows
“hubIssue”: {
“Jira_Account__c”: “Sales Ops Test Account”,
“voters”: ,
“fixVersions”: ,
“internalMap”: {
“Jira_Account__c”: “Sales Ops Test Account”

is this because the Field in Salesforce is a Text Field? Should I try the Account Name field instead

2

Just tested this on my side, and it works. I think the piece about the dereferencing is to blame. Looking at the payload, I would try:
issue.customFields."Client Impacted Test".value = nodeHelper.createOption(issue, "Client Impacted Test", replica."Jira_Account__c")

If you look at the payload, there is no value attribute at all as it is a text field.

Hopefully, this does the trick!

Thanks
Majid

6

Now if a new Case is opened and a value is selected that has this customer name will exalate recognize this value already exists or will it create a duplicate option

Awesome will test, we are also considering Creating a Picklist Field in SFDC so then I would use Value.Value again correct.

7

Yes, it will recognize the value and not create a duplicate - but I would encourage you to try.

About the picklist, indeed, .value.value again!

Thanks
Maiid

8

this seems to be working perfectly, great job @Majid ! I also tested choosing the same Account Name on Two separate cases which are on Two Separate Exalate Connections (one for bug one for new feature) and even though they are separate connections completely but share the same scripts exalate recognized they were the same Value and did not duplicate!

I even went into the JIRA custom field to check the options and there are no duplicates

1 Like
9

Glad to hear! And thanks for confirming!

Have a good day
Majid

10

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.