> 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.107.md).
# Getint Version 1.107
### Release date: May 21, 2026
### Overview
Version 1.107 introduces enhancements to scripting flexibility and attachment synchronization reliability, alongside improvements to hierarchy management in Jira and sub-item identification in Monday integrations.
#### New Features and Improvements
* **Advanced Scripting Enhancements**: Dynamic field scripts now support the reuse of functions from the scripts library, improving modularity and efficiency.
* **Attachment Handling**: Resolved an issue where forward slashes in attachment filenames were incorrectly interpreted as subdirectories, ensuring reliable synchronization across various applications.
#### App Changes and Bug Fixes
* **Jira**: Enabled hierarchy support for Epics, allowing them to be linked to initiatives as parent items for improved project structure management.
* **Monday**: Fixed an issue in the sub-item discovery process where incorrect board names were used when boards had similar naming conventions.
#### Contact Us
If you have any questions, encounter issues, or need further assistance regarding this release, please feel free to reach out to us:
* **Support Email:**
* **Help Center:**
Our team is here to ensure an *effortless* experience for you. Don't hesitate to get in touch!
---
# 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.107.md?ask=&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.
