Auto-assign based on Component when Moving a ticket between projects

Somehow I must have mucked up a configuration so when tickets are moved from Project 1 to Project 2 they are no longer getting auto-assigned to the component lead. Any suggestions on where to look? I noticed that the ASSIGNEE field is no longer visable on the Step 3 of 4 of the Move Issue Update Field Screen.

1 answer

1 accepted

This widget could not be displayed.

Figured it out. If the Assignee in Project 1 is a valid user in Project 2, then the Assignee remains the same and does not trigger a reassignment/notification to the component lead. Note that even 'unassigned' is a valid user in both projects.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in Teamwork

What teamwork quotes inspire you?

Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork?  We've compiled a list here, along with...

134 views 16 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you