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

# Getint Version 1.96

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

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

This release introduces **Dynamic Fields** for advanced field mapping and scripting, along with usability and validation improvements across the platform. App updates include fixes for **GitHub** quickbuild and **Jira** work item property updates.

#### New Features and Improvements

* **Dropdown usability fix**: Reopening dropdowns now preserves filter input.
* **Dynamic Fields**: A major enhancement that allows users to manage unsupported or custom fields through scripting.
  * Fields can be defined and mapped in integrations, with values calculated dynamically at runtime.
  * Enables advanced field mapping, supports complex business logic, and reduces the need for custom development.
  * Supported types: **String**, **IdLabel**, **Number**, and **Date**.
* **Multi-field mapping improvements**: Duplicate field mappings are now automatically prevented before configuration is applied.
* **Shared mappings validation**: Users can only select shared mappings that match the integration direction.

#### App Changes and Bug Fixes

* **GitHub**: Fixed quickbuild for Projects-type integrations.
* **Jira**: Work item properties now update correctly when items move between projects.

#### 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.96.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.