-
Suggestion
-
Resolution: Won't Do
-
None
-
None
Problem Definition
After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce or Microsoft Dynamics), not all the fields are available for selection or if the field is available, there's an id instead of display value
Suggested Solution
Provide a way to integrate all fields that users are expecting to leverage and indicate which fields did not come through after integration
- is related to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[API-61] As a Jira user, I cannot view all fields that refer to other CRM entities
The comments are old, but still relevant and completely false advertising. For Microsoft Dynamics CRM, the documentation (https://confluence.atlassian.com/jiracorecloud/crm-for-jira-cloud-950809846.html?_ga=2.33377596.304245046.1559586519-1171770769.1555682478&_gac=1.44901264.1557518687.EAIaIQobChMIyvH-5OGR4gIVwh-GCh2Y2QonEAAYASAAEgKXZfD_BwE)
clearly states the following:
- Accounts: all default and custom fields, related cases, related contacts, related leads, and related opportunities
- Contacts: all default and custom fields, related leads, related opportunities
We need these custom fields to be accessible and populated with the right values (currently they bring in what appear to be line numbers from the table) in order to fully utilize this function.
Thanks for the report, this is certainly a valuable enhancement to the integration! At the moment we support all 'primitive' fields that are embedded directly on the CRM record, but we don't fetch additional data about the other CRM records linked to the one you are viewing (under the hood, Salesforce provides us with an opaque ID for linked records, which is of little use for display in Jira). We intend to support this in the future, but don't have a firm timeline at this stage. There are a few concerns around performance—as we'll need to make additional requests to Salesforce to look up the linked records—that will need to be thought through first.
Thank you for pointing out the inconsistency in our documentation. I'm reaching out to our technical writing team to amend the documentation to set clearer expectations about the current functionality. We'll update this ticket with progress on the feature itself when we have a chance to address it.
cheers,
Tim
Hi Michael, Tim, and Jason,
Can you please change this back to a bug?!?!
This is NOT an improvement! The integration does not pull in default fields as it states it should. It DOES NOT pull in custom fields as it states it should. I would consider that to be a defect in that it is not performing it's basic function.
We really need this to addressed.
*note: it is in this document that it clearly states "all default and custom fields". It does not actually pull over all default and custom fields and we have yet to even learn which ones it picks and chooses.
https://confluence.atlassian.com/jiracorecloud/crm-for-jira-cloud-950809846.html
jworley I don't believe the component on this issue Issue - Fields is set correctly, but I don't see another component that is more applicable. I would have expected something around Ecosystem Apps but it doesn't seem to exist.
Looking at the CRM-42 issue you linked, this seems to be more of an improvement than a bug. I will change the issue to reflect this.
Jira Cloud for CRM has been deprecated https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Deprecating-the-Jira-Cloud-for-CRM-app/ba-p/2054735.