It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Answer accepted

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
Published in Teamwork

Listening out loud: how Fabian Lopez works on distributed teams

The start of the COVID-19 pandemic served as a forcing function to re-evaluate the way teams worked together. In fact, many companies are re-learning how to collaborate with their teams. As some move...

58 views 2 1
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you