Alternate way to link duplicates as an automation rule

[Robert Munoz]

Does anyone know if duplicate issues can be identified using Advanced Branching that requires a smart value or am I off track?? Here is what I have but not working. I'm not sure of where the smart value fits in mainline or branch? Process: if {reporterEmail} matches with {issue.reporter.emailAddress} and issue regex {triggerTraceback} with {issue.description.match("")} then Link. Any help appreciated.

[Ignacio Pulgar]

Hi @Robert Munoz ,

This is an interesting use case!

I have not tried anything similar before, but I think I would try:

• compare with issues created in the last 7 days or so
• matching the same Reporter
• with the same Summary length
• with the same Description length

Probabilistically, the chances that such a rule ended up linking two non-duplicated issues is very low and is likely to perform better than comparing word by word.

Hope it helps.

[Robert Munoz]

Thank you for the advice @Ignacio Pulgar  I haven't determined a distinction between the two branch options Advanced Branching and Branch Rule and whether I can find duplicate links using automation with some other branching option (say JQL or issue.description.match() for instance) without using the Branch Rule/Similar Issue description slider. I'm going to continue to pursue the idea of using key word identification in the description field of the issue since we have several use cases where it would be helpful. 

That being said. I have an audit snap shot showing the the keyword search is picking up but I think I'm matching the trigger issue with itself instead of matching all issues in the branch. 

[Robert Munoz]

I seem to have answered my own question of linking with the use of the Similar Description Slider. However, when I add a Transition Issue to 'Done' (or 'Canceled') only the last linked issue is shown. Anyone know why that happens? If all issue status' are left as-is, the links are all shown linked to the most recent issue.