Redirected from Exalate Support portal
Hi All,
We are facing an issue related to the assignee assignment logic in the Exalate plugin during the synchronization from our IFS Jira instance (source) to the DTP Jira instance (target).
Summary of Current Behaviour:
DTP Side assignee is mandatory for ticket creation.
During sync from IFS to DTP, Component is a mandatory field.
When a component is selected in IFS, the same component exists in DTP.
On the DTP side, the incoming script is configured so that:
If no component is provided, a default assignee is assigned.
If a component is provided, the component lead should be assigned as the assignee.
This logic is functioning correctly during the initial issue creation.
Issue We Are Facing:
If any user on the DTP side manually updates the component or manually changes the assignee, the assignee does not get updated automatically based on the new component value.
In other words, the Exalate Plugin’s incoming script updates the assignee only at the time of issue creation, but not when component/assignee is changed afterward.
We need the plugin to re-evaluate and update the assignee in the following scenarios:
When the issue is created via IFS → DTP sync (already working).
When the component is manually changed in the DTP issue.
Expected behavior:
If component is empty → assign default project lead as assignee.
If component has a value → assign corresponding component lead as assignee.
This logic should apply not only on creation, but also on any field update involving component or assignee.
Request:
Please review this scenario and let us know if the Exalate Plugin can support:
A re-evaluation trigger on field updates, or
An enhancement in the incoming script to reapply the assignee assignment logic whenever component/assignee changes.
Please advise the best possible solution or configuration.