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

# Getint Version 1.75

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

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

This release introduces an array of new features, significant performance enhancements, and essential bug fixes, all aimed at delivering a smoother and more efficient user experience when using Getint.

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

* Added an option to disable multi-mapping fields for better customization.
* Enhanced logging to improve visibility into license-related issues.
* Clearer guidance on setting migration time ranges.
* New support for concatenating multiple fields, adding more flexibility to data mapping. More information about this feature [here.](https://docs.getint.io/guides/integration-synchronization/how-to-map-fields#concatenating-fields)

#### Bug Fixes <a href="#bug-fixes" id="bug-fixes"></a>

* Fixed an issue where duplicate settings triggered incorrect license errors.
* Resolved a bug where the field mapping direction was being reset unexpectedly.
* **Jira DC**: Fixed an issue where the full list of available fields wasn't loading correctly.

#### 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%2FgbLVeOC6GBLfcKSZlslk%2FGetint%20Banner%20-%20Schedule%20a%20Demo.jpg?alt=media&amp;token=10fa8965-4eab-45bf-a279-5f13937d9b1e" 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.75.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.