When there is multiple case association to a single jira issue, the data synced in a string field will be overwritten by the newer sync.
This is expected as a string field will not concatenate, but replace an existing value.
This feature request is to have the string field concatenate with the previous values.
Immanuel Siagian
| Hosting platform | Cloud |
Particularly useful when linking accounts with feature requests or bugs, to be able to easily see a list of affected customers, as well as potentially a sum of the annual revenue represented by those accounts.
Attachments Open full size
It is important to be able to represent multiple Jira issues in Salesforce custom fields so they can be exposed on the customer portal (Experience Cloud). Otherwise the product is missing an important use case the disqualifies the product from our selection process.
Attachments Open full size
Maybe, we can add a scenario where there are multiple fields with one sync direction from Salesforce to Jira as well.
Attachments Open full size
+1
Attachments Open full size