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

# Getint Version 1.77

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

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

This release brings a variety of new features, important performance improvements, and crucial bug fixes, all designed to provide a better and more reliable experience with Getint.

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

* Optimized sync log writing to prevent Getint from hanging.
* Added new date field operators for UI filters: IS\_AFTER, IS\_BEFORE.
* Script engine now supports Java 1.8+.
* Large Jira/ServiceNow user lists now have pagination and filtering.

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

* Fixed import/export issues.
* Fixed attachment sync issue with accented filenames.
* Getint On-Premise now requires Java 1.8+.
* **Freshdesk/Freshservice**: Added support for cascading fields.
* **Git**: Updated the licensing model, and enabled syncing for commits, branches, and pull requests from public GitHub repositories.
* **Jira**: Added support for "Assignee emails" as a dedicated field.
* **Monday.com**: Resolved issues with Group field mapping, and implemented support for subitem comments.
* **Notion**: Introduced a 2,000-character limit for text fields, and added a single-select option for the assignee field.

#### 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%2FMpfWCYWuzARQUUVwWds5%2FGetint%20Banner%20-%20Schedule%20a%20Demo.jpg?alt=media&amp;token=8f7f10bd-43ee-43f3-b569-5710681b57b7" 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.77.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.