---
title: "Component Error markup://JCFS:JiraAssociation When Associating or Creating Jira Issues"
canonical: "https://support.appfire.com/space/SUPPORT/3421175939/Component%20Error%20markup%3A%2F%2FJCFS%3AJiraAssociation%20When%20Associating%20or%20Creating%20Jira%20Issues"
format: markdown
---
> Macro (toc)

## Environment

- **Product: **Connector for Salesforce & Jira
- **Platform: **Jira Cloud or Jira Data Center with Salesforce
- **Affected component:** Legacy Aura component `JCFS:JiraAssociation`
- **Recommended component:** Jira Issues (NextGen)

## Overview

When users associate or create a Jira issue from a Salesforce record using the Legacy Salesforce Lightning component, the page may show a JavaScript component error or remain in an endless loading state. This issue is limited to the Legacy Aura component. To resolve it, replace the Legacy component with the **Jira Issues (NextGen)** component.

## Symptoms

- After users select **Associate** or complete Jira issue creation from a Salesforce record, Salesforce displays a component error.
- The modal does not close or redirect as expected.
- The page may remain in an endless loading state.
- Users may need to refresh the page manually to continue working.
- The Jira association may still be created successfully in the background.

## Error details

Users may see one or both of the following errors:

```
Uncaught Action failed: JCFS:JiraAssociation$controller$closeModalFromButton [Cannot read properties of undefined (reading 'get')]
```

```
Uncaught Action failed: JCFS:JiraAssociation$controller$createAssociation [Cannot read properties of undefined (reading 'get')]
```

The error popup is typically shown by Salesforce as a component error for `markup://JCFS:JiraAssociation`.

*Example: Legacy Salesforce component error shown after the association flow attempts to close the modal.*

![Screenshot 2025-08-05 220940.png](media://2ea97178-d514-4d44-8051-0379e92240f4)

## Impact

- The user experience is interrupted by an error popup or endless spinner.
- The modal may remain open and cannot be closed normally.
- Users may believe the action failed even when the association completed successfully.
- No data-loss behavior is expected from the JavaScript error itself.

## Cause

This is a known issue in the Legacy component `JCFS:JiraAssociation`. The component can fail when it tries to complete the final UI flow after creating or associating the Jira issue. As a result, Salesforce displays a JavaScript error or leaves the page in an unresolved loading state. The underlying association and sync behavior may still complete successfully.

## Diagnosis

1. Open the Salesforce record where the Jira issue was associated or created.
2. Confirm whether the page displayed either a component error popup or an endless loading spinner.
3. Check the page layout to confirm the record uses the Legacy Jira component rather than Jira Issues (NextGen).
4. Refresh the Salesforce record and verify whether the Jira association appears in the Jira Issues panel.
5. If the association is present after refresh, the issue is limited to the Legacy component UI flow rather than the association itself.

<details>
<summary>How to recognize the Legacy component</summary>

The Legacy implementation is the Aura-based component `JCFS:JiraAssociation`. If the error popup mentions this component descriptor or the page layout uses the older Jira Issues component instead of Jira Issues (NextGen), the page is affected by this known behavior.
</details>

## Solution

Replace the Legacy component with the Jira Issues (NextGen) Lightning component.

1. In Salesforce, open the **Lightning App Builder** for the affected record page.
2. Remove the Legacy Jira Issues component from the page layout.
3. Add the **Jira Issues (NextGen)** component.
4. Save and activate the updated page.
5. Test the association flow again from the Salesforce record.

> ✅ After migrating to Jira Issues (NextGen), the Legacy component error and endless loading behavior should no longer occur in this flow.

> ℹ️ If you cannot migrate immediately, refresh the Salesforce page after the error or endless loading state and verify whether the association was created successfully.

## Related articles

- [https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/3370025067](https://appfire.atlassian.net/wiki/spaces/SUPPORT/pages/3370025067)
- [https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1873543771](https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/1873543771)