-
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
-
JSWCLOUD-17484 Add existing custom fields to team-managed projects e.g. Tempo fields
- Closed
[API-61] As a Jira user, I cannot view all fields that refer to other CRM entities
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
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 |
Link |
New:
This issue is related to |
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 |
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 |
Assignee | Original: Vitalii Saienko [ vsaienko ] |
Assignee | Original: Tanguy Crusson [ tcrusson ] | New: Vitalii Saienko [ vsaienko ] |
Workflow | Original: JAC Suggestion Workflow [ 3127657 ] | New: JAC Suggestion Workflow 3 [ 3588386 ] |
Assignee | Original: Tim Pettersen [ tpettersen ] | New: Tanguy Crusson [ tcrusson ] |
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 h2. Workaround (Optional) No workaround currently available |
New:
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 |