Hello everyone, my name is Tehreem and I'm experiencing difficulties in implementing automation for issue assignment. I have set up automation rules where any issue type labeled as 'BUG' should be automatically assigned to the QA Team lead. However, despite my attempts, this automation doesn't seem to be working. On the same project, I've also implemented automation where issues with types like 'Change request,' 'Feature,' or 'EIPC' are assigned to the Project Manager, and this automation is functioning correctly.
JQL Querry: issue type = Bug AND assignee in (630c965eea661fd37d4e6c99, 62b41b5267dff38e09888d59) order by created DESC
I have attached screenshots to provide more context. Can you please assist me in identifying what might be going wrong with the automation for assigning bugs? Thank you.
Hello @tehreem_warsi
What information is in the Audit Log for the execution of this rule?
I believe your problem is the two conditions:
To get past the first condition the created issue must be a Bug.
Then to get past the second condition the issue must be a Sub-bug.
Both conditions must be met in order for the rule to continue running.
An issue has only one value for issueType, so there is no way both of these conditions can pass.
Hi Trudy,
Thanks for replying, can you please tell me what should I do now? Kindly share the correct steps, because I already tried multiple things but not getting desired results.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You said you want to automatically assign issues that are Bugs.
If that is the case, why are you checking to see if the issue type is "Sub-Bug"?
If you want to automatically assign issues that are Bugs, then remove the condition that is checking if the issue type is Sub-Bug.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.