We use JiraSD next-gen also for communication with other service desks. Many service desk use unique summary to identify the object (and issue related to this object). Jira mail handler can add comments to issue only based on its key or message sequence (in-reply-to). As a result, we end up with many open issues with very similar names (summaries) that need to be iterated over manually in order to collect comments on the original issue.
The question is how to automate this process? Please advise!
I can sort the issues I need by summary, but how do I link them based on the summary? Automation allows you to link issues based on a key.
For example, the original issue summary "Last mile quality issue | site | object", and the next issue summary "Last mile quality restored | site | object".
