> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/support-legal-and-others/platform-releases/getint-version-1.84.md).

# Getint Version 1.84

### Release date: June 20, 2025 <a href="#release-date-february-24-2025" id="release-date-february-24-2025"></a>

### Overview <a href="#overview" id="overview"></a>

We’re excited to announce key enhancements across platforms and apps designed to improve performance, reliability, and data handling. This release focuses on sync accuracy, integration stability, and better field support.

#### New Features and Improvements <a href="#new-features-and-improvements" id="new-features-and-improvements"></a>

* **Smarter Comment Sync**: Improved direction logic for comment synchronization ensures comments now flow accurately between integrated platforms based on configuration.
* **Dependency Link Deletion Support**: You can now delete dependency links directly via sync, offering more control over relationship management.
* **Performance Boost**: Increased database pool size to better handle heavy loads and improve overall responsiveness in high-volume environments.

#### **App Changes and Bug Fixes**

* **Attachment Sync Fixes**: Resolved issues in one-way sync scenarios where attachments weren’t properly synchronized or deleted, ensuring cleaner data integrity.
* **Azure DevOps**: Addressed problems fetching **work item links**, enabling better visibility across linked tasks.
* **Git**:
  * Now supports **pull request statuses**, making it easier to track code review stages.
  * Improved **connection setup** and overall integration usability for a more intuitive onboarding experience.
* **Jira Data Center**: Fixed import issues when integrating with **existing connections**, enhancing reliability for enterprise-scale workflows.
* **Salesforce**: Introduced support for **currency fields**, enhancing financial data tracking and consistency across integrations.
* **ServiceNow**: Added support for setting **parent fields**, giving users more flexibility in structuring incidents and requests.

#### Contact Us <a href="#contact-us" id="contact-us"></a>

If you have any questions, encounter issues, or need further assistance regarding this release, please feel free to reach out to us:

* **Support Email:** <support@getint.io>
* **Help Center:** <https://getint.io/help-center>

Our team is here to ensure an *effortless* experience for you. Don't hesitate to get in touch!

<figure><img src="https://4106311246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MR6Z9V8zLATPQPOGSDf%2Fuploads%2F9OSEDBl869gRue9mQAwv%2FGetint%20Yellow%20Banner.png?alt=media&amp;token=9cc42142-6e48-4931-8fd5-cbf7dcf4cdc1" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team
">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.getint.io/support-legal-and-others/platform-releases/getint-version-1.84.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
