Feature requests

When adding multiple Jira Cloud instances under the same user, the Tool Selection page only shows the user name, which can be confusing an time consuming if you have a lot of connections.

Current situation: In a flow where an item is mapped to create a JIRA ticket, it is possible to have text be included in the JIRA ticket description but not an image. For example: When I create a Clickup task, create a JIRA ticket. Map the Clickup task description to the JIRA ticket description. In this scenario, any images included in the Clickup task description won't show up in the JIRA description. The only way to map over images is via attachments, which doesn't have the same practical uses.

"Linked issues" sections is not synced between two JIRA Cloud instances, even if the linked issues are from the very same project and are present in both instances of the flow. Of course would be awesome this feature would work between projects synchronized from different Unito Flows.

Support syncing Jira Parent field to Wrike to create subtasks under the Parent.

Ability to exclude of syncing Private comments/notes to another Jira

This request is to support Jira initiatives as a parent task with epics nested below. The user would like for the initiative to appear as a task in Wrike and the epic as a subtask. This could be similar to the 'sync epics as parent tasks' feature we currently support in Jira.

Currently, this field can only be synced to the description footer of the other project. The user would like to be able to map Original time Estimate <> Original time Estimate

I have a Wrike - Jira flow. Our data analysis team in Jira creates tickets and links them as "related issues" to our usual tickets. We would like this linked issue field to be supported so users in Wrike can see the related tickets without having access to Jira

Worklog entries (consumed time, reporter, date & comment) are not synced between two Jira instances.

There is a way in Jira to simply "Archive" an issue regardless of the status it is in. As I understand it, the Status being Open vs Open or Archived in Unito refers to the type of the Jira status, and not at all to whether the issue is Archived or not. It would be nice if I could capture whether an issue is Archived or not in my rules for syncing. Attached is the menu option to Archive an issue in Jira.