We are using Exalate between Jira SM and Jira. As a rule, all issues created in JSM are exalated to Jira.
Some issues created initially in Jira are also exalated to JSM. But only a few. We had this specific use case whereby we wanted to update a field on all the Jira issues and – where the issue is already exalated–we wanted to replicate these issues to JSM, so the field would come across. The problem is that the post function “Exalate this issue” will create a new issue in JSM where the existing issue is not already exalated and will update only where the issue is already exalated. This means if I bulk update 2000 issues in Jira and only 20 are currently exalated we would end up creating 1980 issues in JSM, is there a way we can limit exalation to issues that are already exalated?
Question raised:
We are using Exalate between Jira SM and Jira. As a rule, all issues created in JSM are exalated to Jira.
Some issues created initially in Jira are also exalated to JSM. But only a few. We had this specific use case whereby we wanted to update a field on all the Jira issues and – where the issue is already exalated–we wanted to replicate these issues to JSM, so the field would come across. The problem is that the post function “Exalate this issue” will create a new issue in JSM where the existing issue is not already exalated and will update only where the issue is already exalated. This means if I bulk update 2000 issues in Jira and only 20 are currently exalated we would end up creating 1980 issues in JSM, is there a way we can limit exalation to issues that are already exalated?
How comes a post function is triggered?