note

At Caelor, our driving force is you, our customers. This changelog reflects our commitment to being customer-centric, highlighting features that have been prioritized and developed based on your invaluable feedback and requests.

At Caelor, our driving force is you, our customers. This changelog reflects our commitment to being customer-centric, highlighting features that have been prioritized and developed based on your invaluable feedback and requests.


Support for cascading issue pickers in the customer portal

A new feature allows configuring issue picker fields where options depend on the selection in another field. This enables use cases such as selecting sub-tasks based on a previously selected parent issue.

The behavior is configured using the currentIssue("fieldId") placeholder in JQL, which dynamically resolves values from other fields in the same form.


Dynamic JQL placeholder

We have implemented the currentIssue() placeholder to enhance the dynamic referencing of field values within the current issue. Users can now utilize this placeholder by specifying the field name or ID as the function argument. This functionality is designed to simplify the creation of context-sensitive configurations in Jira fields → https://caelor-apps.atlassian.net/l/cp/0iu29ZfM.


Inline Editing

Previously, editing required a dialogue box, but now it’s fully inline, aligning seamlessly with the native Jira experience. This improvement makes editing faster, more intuitive, and consistent with how you interact with other Jira fields.


Jira Service Management (JSM) Support

We are excited to announce that LInksy now fully supports displaying custom fields in Jira Service Management (JSM), a feature that has been highly requested since the beginning. After working closely with Atlassian to overcome previous blockers, we are finally ready to introduce this capability.

For more details, refer to our documentation here. This update is designed to significantly enhance how users work with custom fields in JSM.


Default link type for inline linking in issue panel

Introduced a default link type for inline linking within the Issue Panel. This feature allows users to set a preferred link type that will be applied by default when creating new links, speeding up the linking process and reducing repetitive selections. This is particularly useful for teams that frequently use specific types of links, enhancing consistency and efficiency in issue management.


Updated Forge node.js runtime

This release of Linksy - Advanced Issue Linking introduces significant enhancements including an updated Forge node.js runtime, performance optimizations, and new linking functionalities that streamline workflows within Jira. This significantly enhanced the overall performance of the app. Users will experience faster load times, quicker response to actions, and a more fluid interaction with the issue linking features, especially when handling large volumes of data or complex JQL queries.


Added manage:jira-project to scopes

The manage:jira-project scope has been added to Linksy's required permissions. This update grants the app enhanced capabilities to manage project-level settings and configurations. This scope is essential for performing actions like creating, modifying, and deleting project components, which are integral to advanced issue linking strategies.


Initial release

Linksy - Advanced Issue Linking enhances Jira by allowing users to manage issue links using JQL filters and introduces user-friendly custom fields for an improved linking experience. This initial release focuses on simplifying complex linking tasks and providing greater control over how issues are connected.

Key features: