The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Avoid component assign when there is already someone assigned?

Jeff Santos
Contributor
July 2, 2019

Hi guys,

Does someone knoe if there is a way to avoid components auto assign when there is already another user assigned?

I like this feature, however, when the issue is created and assigned to someone else, it overwrite the assignee, It really bothers me.

It should work only if it is unassigned.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Jeff Santos
Contributor
July 2, 2019

Forget about it guys.

What was causing the components to assign an inssue was an automation of mine that assignes the assignee as "Automatic", forcind the componente lead assign even after the issue is created.

 

All I did was to run this automation only when the user is not an agent.

It worked perfectly. If the user is an agent, it assigns the component lead. Otherwise, it just leaves the current assignee.

 

Thanks!