Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Setting QA Assignee via Round Robin, but QA Assignee should != Developer

leigh.villahermosa June 14, 2024

Hey There!

My team has a Jira cloud project and I'm looking to configure an automation that does a couple of things:

  • When Status = In Review and Label = Ready_for_QA, the following occurs:
    • Assign the Issue based on a Round Robin pool
      • The QA Assignee should != the user in the Developer (custom) field
      • If they =, it should route to the next person in the queue
    • Based on the new Assignee, sets the QA Assignee (custom) field
    • Sets a comment letting the new QA Assignee the ticket is Ready for QA

I need a little help cleaning it up and I'm running into the issue of the automation assignee it to the person in the Developer (custom) field who understandably should NOT QA their own ticket.

Showing below how the automation is currently written:

Screenshot 2024-06-14 at 2.54.03 PM.png 

Any help or advice greatly appreciated! Thank you <3 

1 answer

1 vote
Mikael Sandberg
Community Champion
June 14, 2024

Because of the way the assignee via round-robin works I don't think there is much more clean up you can do. Unfortunately there isn't a way to get the user who would be next in the round-robin so you could compare if that user is the same as the developer.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events