> 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.105.md).
# Getint Version 1.105
### Release date: April 21, 2026
### Overview
This update focuses on deepening our integration capabilities and cleaning up the "under the hood" mechanics to make your synchronization smoother. From supporting the latest Jira versions to ensuring your Salesforce feeds are more expressive, here is what's new.
#### New Features and Improvements
* **Enhanced Run Logs**: We've increased the visibility of HTTP requests within run logs. This makes troubleshooting connectivity and data transfer significantly more transparent.
* **Custom Property Stability**: Fixed a UI bug that caused list items to duplicate when editing Custom Properties. Your lists will now stay exactly as you intended.
#### App Changes and Bug Fixes
* **Jira Data Center**: Full support for Jira 10 and Jira 11. We’ve updated core dependencies to ensure total compatibility with the latest enterprise releases.
* **Jira Cloud**: Optimized license and trial verification logic when using the **JiraRestClient** to search for issues.
* **ServiceNow**: Enhanced detection of the task table to ensure all issue types load correctly within the Getint UI.
* **Salesforce**: Added support for additional comment and feed item types (including **Link Posts**), moving beyond standard **TextPosts**.
* **Wrike**: Refined subitem handling. We've also removed **Subitem** from Type Mapping in scenarios where it isn't supported to prevent configuration errors.
{% hint style="warning" %}
If you are using **Jira Data Center**, we recommend verifying your environment version to take full advantage of the new dependency updates.
{% endhint %}
#### 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.105.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.
