Is there any Atlassian best practice to find & handle duplicate Issues in Jira Service Management?
There can be multiple scenarios which may lead to creation of duplicate issues in Jira Service Management i.e.,
1) The same issue is raised by a customer at different point of time
2) The same issue is raised by 2 different customers at the same time
3) It's a known error and multiple customers are raising the same issue.
In case it's a known error what automation would help?