Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Assigning testing of ticket to someone other than the owner

Currently our team is lacking QA.
For that each developer will test the other developer's tickets.
I need to create an automation to will assign the ticket to someone else other than the person who worked on it when it moved from IN-REVIEW to READY-FOR-TEST

I couldn't create a dynamic list to assign the issue.

Could you please help me?

Thanks a lot in advance.

1 answer

Hey @John Salib 

You can use automation to do this - see print screen below
This way you can create a list of people who JIRA will choose from, you can choose if it will be balanced, or random and you can restrict that this can't be current assignee using JQL :) 


you can restrict that this can't be current assignee using JQL :)

Would you please help me specify that in JQL?

BTW, I already reached that far on my own, but I could't do the JQL part to specify the current assign not to be part of the `User list`. Because `User list` is static.

Okay, so this is what I would call an ugly code if I was a coder, but it should work so ;) 

Try making it kind of a loop - assign to a member of the group and add a Check if the current assignee matches previous one, the rule will be executed again until it gets assigned to someone else.

I went through Community and documentation and I did not find a more elegant way. 


This is genius.
Thanks a lot Marta, I will test it and will keep you posted

@Marta Woźniak-Semeniuk 

I tried your solution but unfortunately I keep getting
`Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):`

I believe that I copied your suggestion word for word.

Do you have any idea why is this happening?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events