Automation rule for similar issues: what's wrong?

[Dolores Rhyme]

The use case is to link similar issues within a project. The rule needs to check 'similarity' when new issue is created.

It seems like a really simple one, but it doesn't work, issues are not linked:

To test the rule I pick any ticket in the project and create the same with slight modifications or without them at all to increase the chances of 'similarity', but Audit log says:

What do I do wrong?

[Aaron Whigham]

Hello Saranya,

Here are a couple of solutions, based on how the project(s) in your Jira instance will use the "QA assignee" field.

1. Will this custom field "QA assignee" be used in all of the projects in your Jira instance?
   If so, then you will have to configure the "Issue Updated" event in your default notification scheme.
   
   (Recommended)
2. If the "QA assignee" will not be used in all of the projects in your Jira instance, then you will have to create a Custom Notification Scheme. A Custom Notification Scheme can be assigned to one or more projects.  Therefore if  you have 30 projects in your Jira instance and the "QA assignee" field is used in 1 project, you can assign one Custom Notification Scheme to that 1 project.  Moreover, making a change to the Custom Notification Field will affect only the 1 project.
   
   You can create many Custom Notification Schemes and assign them to individual projects or a group of projects.
   
   
   

SUMMARY:  I suggest that you create a Custom Notification Scheme for the project(s) that will use the "QA assignee" field.  

Here is a link to documentation on how to create a Custom Notification Scheme.

https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html

Respectfully,

Aaron

cPrime

[Aaron Whigham]

Also, be sure to learn how to configure the "Issue Updated" event in the Custom Notification Scheme.  You will have the option to select a "User Custom Field Value".

Respectfully,

Aaron