---
title: "Release notes 2.2.0-jira10 and 3.1.0-jira11"
canonical: "https://support.appfire.com/space/477986818/3504079200/Release%20notes%202.2.0-jira10%20and%203.1.0-jira11"
format: markdown
---
**Release date**: 8/11/2026

This page outlines the updates included in the latest release of Connector for Salesforce and Jira DC.

**Jira compatibility**: Jira Data Center 10.x, Jira 11.x

---

# New features

The following features are included in this release:

- **Bulk pull for associated Jira issues**: Added **Bulk Pull** to *Bulk Operations*, so you can pull the latest Salesforce data into multiple already-associated Jira issues at once, using the same JQL search and workflow as **Bulk Push**. For details, see [Pull Salesforce updates for Jira issues in bulk](https://appfire.atlassian.net/wiki/spaces/477986818/pages/3442049074).
- **Trigger code when an association is unlinked**: You can now subscribe to the *Unlink* event to run custom Apex code when a Jira issue and Salesforce record association is removed. For details, see [Trigger code when an association is unlinked](https://appfire.atlassian.net/wiki/spaces/477986818/pages/2560920173).
- **Sub-task creation from Salesforce**: You can now create Jira Sub-tasks directly from Salesforce. When you select a Sub-task issue type in the *Create/Associate Issue* dialog, a required **Parent** field appears so you can choose the Jira issue the Sub-task should belong to. Standard issue types are unaffected. For details, see [Create a Jira issue from Salesforce](https://appfire.atlassian.net/wiki/spaces/477986818/pages/2560558488).

---

# Bug fixes

The following bugs are fixed in this release:

- Fixed an issue where the **Cancel** button didn't work when creating a Salesforce object.
- Improved **Bulk Pull** error handling for view-only associations, so these cases are handled correctly and give you clearer feedback.

---