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

0 votes
Accepted answer

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
Community showcase

Scrum Roles Explained: the Do's and the Don'ts

Hello Community,  Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...

63 views 0 4
Read article

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