> 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.73.md).

# Getint Version 1.73

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

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

This update introduces several improvements to enhance performance, usability, and integration across platforms and applications.

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

* Added the ability to include extra Java arguments when using `JAVA_CMD`.
* Extended cloud HTTP request logging to 60 minutes for better tracking.
* Improved item status transitions for a smoother workflow.
* Made `CONTAIN` filters case-insensitive, ensuring more flexible search functionality.

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

* Fixed an issue where the same field could be mapped multiple times incorrectly.
* **Azure DevOps**: Enhanced synchronization for iteration paths, improving project tracking.
* **HubSpot**: Better searching for items eligible for synchronization.
* **Jira**: Introduced support for request types in Jira Service Desk (JSD), streamlining ticket management.
* **Monday**: Added support for number-based fields.
* **Salesforce**: Expanded support to include Date and Checkbox fields for more precise data handling.

#### 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%2FkpvWPz2hyYUxbfLSoAav%2FGetint%20Banner%20-%20Schedule%20a%20Demo.jpg?alt=media&amp;token=be199b28-47a6-45a8-8389-cbe252b6078b" 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.73.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.