Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-61

As a Jira user, I cannot view all fields that refer to other CRM entities

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Jira Cloud for CRM
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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 

       

            [API-61] As a Jira user, I cannot view all fields that refer to other CRM entities

            Vitalii Saienko (Inactive) made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Vitalii Saienko (Inactive) added a comment - 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 .
            Vitalii Saienko (Inactive) made changes -
            Description Original: h2. Problem Definition

            After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce or HubSpot), not all the fields are available for selection or if the field is available, there's an id instead of display value
            h2. 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 

             
            New: h2. 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
            h2. 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 

             
            K. Yamamoto made changes -
            Link New: This issue is related to JSWCLOUD-17484 [ JSWCLOUD-17484 ]
            Vitalii Saienko (Inactive) made changes -
            Description Original: h2. Problem Definition

            After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce or HubSpot), not all the fields are available for selection 
            h2. 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 

             
            New: h2. Problem Definition

            After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce or HubSpot), not all the fields are available for selection or if the field is available, there's an id instead of display value
            h2. 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 

             
            Vitalii Saienko (Inactive) made changes -
            Description Original: h2. Problem Definition

            After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce), not all the fields are available for selection 
            h2. 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 

             
            New: h2. Problem Definition

            After configuring integration with the CRM for Jira Cloud add-on (i.e., with Salesforce or HubSpot), not all the fields are available for selection 
            h2. 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 

             
            Vitalii Saienko (Inactive) made changes -
            Assignee Original: Vitalii Saienko [ vsaienko ]
            Vitalii Saienko (Inactive) made changes -
            Assignee Original: Tanguy Crusson [ tcrusson ] New: Vitalii Saienko [ vsaienko ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3127657 ] New: JAC Suggestion Workflow 3 [ 3588386 ]

            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.

             

            Matthew Gore added a comment - 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.  

              Unassigned Unassigned
              jworley Jason Worley (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: