Use JQL to report on Jira issues with associations

Associations made with Salesforce from Jira are recorded in the issue's fields. This guide explains how those fields can be viewed and used as Jira Query Language (JQL) filters for reporting purposes.

On this page: 1 Version differences 1.1 Jira Cloud 1.2 Jira Server 2 Creating an association 3 Using JQL to filter association fields 4 Related information

On this page: 1 Version differences 1.1 Jira Cloud 1.2 Jira Server 2 Creating an association 3 Using JQL to filter association fields 4 Related information

This feature uses the following Jira fields when the application is installed:

Associations - displays a list of associated Salesforce Objects.
Association Count - displays the amount of associated Salesforce Objects.

For the application to be able to populate and update the Associations and Associations Count fields, they should be added to the Edit Issue Screen. An administrator is required to configure the fields in the project settings.

If the fields are not added to the Edit Issue Screen, they cannot be updated.
If the fields are added to the View Issue Screen, they are editable and can be edited manually. We recommend removing these fields from the View Issue screen and avoiding updating them manually.
If the fields are updated manually, the application will sync them again when the next association-related action occurs.

For more information regarding screen configuration, refer to Configure the issue detail view.

You can use these fields to search Jira issues through the issue navigator. For example, to search for issues associated with a specific Salesforce object, or issues with a specific number of associations.

Version differences

Jira Cloud

By default, the fields are empty; they will be populated on the following association-related actions (eg, issue being associated).

Jira	Salesforce

Jira	Salesforce
A Salesforce object is created for the issue.	A Jira issue is created for the object.
A Salesforce object is associated with the issue.	A Jira issue is associated with the object.
The issue is unassociated (unlinked) from a Salesforce object.	The object is unassociated (unlinked) from a Jira issue.
A Salesforce object is created (and associated with the issue) through workflow post-function.

Jira Server

If the Associations and Associations Count custom fields are not created, disable and enable the app.
Configure the field configuration and update renderers for Associations field to Wiki Style Renderer to avoid the field context looking broken.

By default the fields are empty, but they will be populated when the Jira Issue is updated and if there is an association for the issue.

Jira	Salesforce

Jira	Salesforce
A Jira issue is updated.

Creating an association

Open a Jira issue from a project that is bound with Salesforce. You can see the Associations and Associations Count fields are empty.
If they are already populated, go to the next step. Otherwise, to populate those fields, check out Configuring an association on how to create an association between Jira issues and Salesforce.

If the association has been created before this feature was implemented, the Associations and Association Count fields will still be empty despite having an association. You will have to Create a Salesforce Object from Jira or Configure a new association with a Salesforce Object.

We recommend unlinking the existing association and linking it back again to trigger the update for the Associations and Association Count fields.

Using JQL to filter association fields

In Jira, select Filters > select Advanced issue search.
Next, select More > check Associations and Association Count options. Filter the other fields relevant to your report.
Search for issues associated with a Salesforce Object with a specific Object ID.
Search for issues with specific counts of association.